Source-to-Pay (S2P): What It Means and Includes

1. What are the stages of source-to-pay?

Source-to-pay runs through five stages: sourcing (identifying and selecting a vendor), contracting (negotiating rates, terms and volume commitments), purchasing (issuing a purchase order against the contract), invoice processing (receiving and validating the vendor's bill) and payment (releasing funds and closing the transaction). Each stage produces a record the next stage should reference, so the chain only holds if every stage actually reads the one before it.

In practice these stages are handled by different teams on different software. Procurement owns sourcing and contracting, often in a separate contract repository or spreadsheet. AP owns invoice processing and payment, usually inside the ERP. The purchase order is meant to be the bridge: it should carry the negotiated rate forward so the invoice can be checked against it.

That bridge fails in a specific, mechanical way. A purchase order commonly carries a quantity and a price, but it does not always carry the full contract terms: a volume tier that only applies past a threshold, a rebate clause, a surcharge schedule with an expiration date, a not-to-exceed cap. Three-way matching checks the invoice against the PO and the receipt.

It does not test whether a surcharge on the invoice still meets the condition that made it valid in the contract.

The result is a process that can be procedurally correct at every stage, sourcing negotiated well, the PO matched the invoice, and still pay against terms the contract no longer supports.

1. Sourcing: Vendors are identified and selected, and pricing is negotiated at a category level before any single purchase order exists.
2. Contracting: Rates, volume tiers, rebate clauses, surcharge conditions and not-to-exceed caps are set down in a signed agreement.
3. Purchasing: A purchase order is issued against the contract, carrying forward whatever terms were captured on the PO template.
4. Invoice processing: The vendor's bill is received and checked, typically against the PO and the receipt of goods or services.
5. Payment: Funds are released and the transaction is closed, often the last point at which a mismatch could still be caught.

2. How does source-to-pay differ from procure-to-pay?

Procure-to-pay starts at the purchase order and ends at payment; it is the operational half of the chain. Source-to-pay adds the two stages before that: sourcing the vendor and negotiating the contract. The distinction matters because the terms that later govern an invoice, the rate card, the volume tier, the rebate clause, are set during sourcing and contracting, stages that a procure-to-pay system never touches.

A procure-to-pay system, and most ERP modules described that way, starts its record-keeping at the purchase order. It can match an invoice to a PO and a receipt with precision. What it cannot do is tell you whether the price on that PO still reflects the contract, because the contract itself usually lives outside the system, in a PDF or a contract repository the procure-to-pay module never reads.

Source-to-pay is the wider frame that includes where those terms originate. Naming the difference matters for one practical reason: a gap that opens between the contracting stage and the purchasing stage will never show up in a procure-to-pay system's own matching logic, because that system was never given the contract to match against in the first place.

Invoice-to-contract matching, by contrast, starts at the contract itself and checks the invoice directly against its terms, skipping the PO as the intermediary and closing the gap procure-to-pay leaves open.

3. Where in source-to-pay does margin drift enter?

Margin drift enters at the handoff between contracting and purchasing, and again between purchasing and invoice processing. Terms negotiated in the contract, a volume tier, a rebate clause, an escalation index, a not-to-exceed cap, have to survive two translations before they reach the invoice check. If either translation drops a condition, the invoice can pass every internal control and still not match what was signed.

The pattern repeats across categories rather than concentrating in one. A freight contract's accessorial rate can persist on invoices after the negotiated cap should have capped it. A staffing contract's overtime premium can be billed at the wrong multiplier because the PO carried a base rate and nothing else.

An IT services contract's not-to-exceed clause can be exceeded quietly because nothing in the purchasing stage flags the ceiling.

Each of these is a different mechanism, not a different severity ranking, and each is described on its own terms rather than compared against the others. What they share is a structural cause: the contract term existed, and the stage that was supposed to carry it forward into the invoice check did not.

See margin drift vs. legitimate price increases for how to tell a real contract violation from a price change the vendor was entitled to make.

4. How is source-to-pay typically evaluated for gaps?

Evaluating a source-to-pay process for drift means testing the handoffs, not the stages in isolation. That means pulling the actual contract terms, not just the PO price, and checking recent invoices line by line against rate cards, volume tiers, rebate clauses and expiration conditions. A stage-by-stage review of matching rules alone will not surface this, because those rules were never given the contract to check against.

A useful diagnostic starts from the contract and works forward, rather than starting from the invoice and working backward. Starting from the invoice tests whether the invoice matches the PO, a check most ERPs already run. Starting from the contract tests whether the PO, and everything downstream of it, still reflects what was actually signed.

That forward-from-contract review is the same logic behind a freight and 3PL audit, a contract labor and staffing audit, or an IT and professional services audit: each pulls the governing contract first and checks invoices against it directly, category by category, rather than relying on whatever matching rule the ERP already applies at the purchasing stage.

For the wider pattern this sits inside, start with the margin drift guide.

5. Frequently Asked Questions (People Also Ask)

Is source-to-pay the same as procure-to-pay?

No. Procure-to-pay covers the purchase order through payment. Source-to-pay is broader: it includes vendor sourcing and contract negotiation before any purchase order exists. The extra stages matter because the contract terms that later govern an invoice are set there, not inside procure-to-pay.

What software handles source-to-pay?

Different companies split it differently. Some use a single source-to-pay suite covering sourcing through payment. Many run separate tools: a contract repository or spreadsheet for sourcing and contracting, and an ERP module for purchasing, invoicing and payment. The split itself is often where a contract term stops being carried forward.

Why does margin drift happen even with a formal source-to-pay process?

A formal process can still lose information at the handoff between stages. A purchase order typically carries a price and a quantity forward, not the full contract, so a volume tier, rebate clause or expiration condition set during contracting may never reach the invoice check at the payment stage.

Does three-way matching catch contract violations?

Three-way matching checks the invoice against the purchase order and the goods receipt. It does not check the invoice against the underlying contract terms, so it will not catch a surcharge that has expired, a rebate that went unapplied, or a rate that no longer matches the negotiated tier.

Where should a source-to-pay review start if you suspect drift?

Start from the contract, not the invoice. Pull the signed rate card, volume tiers, rebate clauses and any not-to-exceed caps, then check recent invoices against those terms directly, category by category, rather than relying on the ERP's existing PO-to-invoice matching.

Is source-to-pay only relevant to large purchases?

No. Drift between contract and invoice shows up across categories regardless of transaction size, including recurring smaller charges like accessorials or Class C consumables, because those are exactly the line items least likely to get a manual second look before payment.

What's the difference between source-to-pay and invoice-to-contract matching?

Source-to-pay describes the entire process from vendor selection to payment. Invoice-to-contract matching is one specific check within that process: comparing an invoice line by line against the contract's rate card, tiers and clauses, rather than just against the purchase order.

Can a company have a clean procure-to-pay process and still have margin drift?

Yes. A procure-to-pay process can match every invoice to its purchase order correctly and still pay against terms the underlying contract no longer supports, because that matching never checks the contract itself, only the PO.