Source to contract is the front end of procurement: identifying a need, finding and qualifying suppliers, running sourcing events, negotiating and signing the contract, before any purchase order or invoice exists. It is the decide and commit phase. Source to pay extends it through supplier onboarding, invoicing and payment.
Ask a CFO where procurement value is created and the sharp answer is not the invoice. It is the decision made months earlier: which supplier, at what price, on what terms. That decision is source to contract, and it is the part of procurement most likely to lose value when sourcing and contracting run in separate tools.
What does source to contract mean?
Source to contract covers the procurement lifecycle from the moment a need is identified to the moment the contract is signed. Where source to pay continues into supplier onboarding, invoicing and payment, source to contract stops at the executed agreement. Think of source to contract as decide and commit, and the pay side as execute.
The term matters because it names a handoff. Sourcing is usually run by procurement and contracting by legal, and the two often work in different systems. source to contract treats them as one process with one record.
What are the stages of source to contract?
- Step 1 Request The business raises a need, with scope and budget
- Step 2 Source RFI, RFQ or RFP events select the supplier
- Step 3 Negotiate Price, service levels and risk allocation are agreed
- Step 4 Contract The terms are drafted, reviewed, approved and signed
AI contract lifecycle management- Sourcing: identifying, qualifying and selecting suppliers, usually through RFI, RFQ and RFP events.
- Negotiation: agreeing pricing, commercial terms, service levels and risk allocation, often over several rounds.
- Contracting: authoring, reviewing, approving and signing the agreement that captures all of the above.
Supplier onboarding often runs alongside the last two stages, so the winner is verified before the contract is signed and the first order can follow straight away.
Why is source to contract where procurement value is won or lost?
The supplier you select and the terms you sign set the cost, risk and value of a purchase. Purchase orders, invoices and payments then execute against those decisions. A strong price negotiated in sourcing only matters if it survives into the contract, and then into the invoice check.
It is also where value most often leaks, for a specific reason. An RFP is awarded in one system, the contract is drafted from scratch in another, and the negotiated terms are retyped by hand. Discounts, service levels and obligations go missing in between, and the savings never reach the enforceable document.
The winner is recorded in a spreadsheet or sourcing tool. Legal hears about it by email.
Pricing and service levels are retyped into a blank template, with room for error.
Onboarding starts after signature, so the first order waits.
Nobody can find why this supplier won or what it promised in its bid.
What is the difference between source to contract and source to pay?
Source to contract is the front end. Source to pay is the whole journey, from the first need to the paid invoice.
| Aspect | Source to contract | Source to pay |
|---|---|---|
| Starts at | A sourcing need | A sourcing need |
| Ends at | The signed contract | The paid invoice |
| Includes | Sourcing, negotiation, contracting | source to contract plus onboarding, purchasing, invoicing and payment |
| Phase | Decide and commit | Decide, commit and execute |
| Main owners | Procurement and legal | Procurement, legal, finance and accounts payable |
source to contract is the strategic front half of source to pay.
For the transactional side of the same comparison, read source to pay vs procure to pay.
How do you connect sourcing and contracting?
Run them on one record, so the award becomes the start of the contract. In Aavenir, RFPflow passes the winning supplier, the awarded lines, the value and the source event to Contractflow in one click. On ServiceNow Sourcing and Procurement Operations, the award also updates the original sourcing request.
After signature, Obligationflow turns the contract's commitments into owned tasks, and Invoiceflow checks invoices against the signed terms, so the price agreed at award is the price that gets paid. The step by step view is on the source to contract page.
A connected use case: an RFP award in RFPflow becomes a contract in Contractflow.
What results have teams published from connecting source to contract?
A global mining company that runs 80 to 100 tenders a year for critical mining services had procurement happening outside its contract lifecycle management platform, no central contract repository and tender awards that did not flow into contracts. It moved tendering, vendor risk assessment, awards and post signature management to RFPflow, Onboardingflow and Contractflow on ServiceNow.
Source: leading mining company case study.
A Fortune 500 insurer in North America gave more than 8,000 requesters one intake that becomes either a contract or an RFx, and reports a 70% faster contract cycle. Read the insurer's story.
When is a connected source to contract platform not worth it?
If you run only a handful of sourcing events a year and most contracts are simple renewals on your own paper, a shared intake form and a disciplined handoff may be enough. Connecting sourcing and contracting pays off when events are frequent, awards are split across suppliers, or contracts carry negotiated pricing and service levels that someone has to enforce later.
A platform also will not fix an unclear process. Agree who owns the award, who drafts the contract and which template applies before you connect the tools.
The bottom line
Source to contract is the front half of procurement, where the supplier and the terms are chosen. Run it on the same record as the rest of source to pay, and the deal you negotiate is the deal you get, at signature and on every invoice after it.