What is procurement in finance and accounting?

Sourcing is finding and negotiating with suppliers (the "who" and "at what price"). Purchasing is the transactional act of ordering (the "buy" itself - requisitions, POs, receiving). Procurement is the umbrella covering both, plus the policy, approvals, and controls around them. Mid-market finance teams typically own purchasing and the controls; dedicated sourcing comes later, if at all.

Procure-to-pay is the connected workflow from purchase request through approval, ordering, receiving, invoice processing, and payment. The defining idea is connection: the request that authorized the spend, the PO or card that fulfilled it, the receipt that confirmed delivery, and the invoice that bills for it all reference each other, so finance controls spend before it happens instead of reconstructing it afterward.

A simple version: (1) an employee submits a request with what they need and why; (2) approvers - manager, budget owner, finance - review it against budget and policy; (3) the approved request becomes an outcome: a PO sent to a vendor, a card, or an internal work order; (4) goods or services are received and confirmed; (5) the invoice arrives and is matched to the order and receipt; (6) payment is approved and executed; (7) everything posts to the ERP with a complete audit trail.

Yes - they're interchangeable terms for the same request-through-payment workflow. "Purchase-to-pay" is slightly more common in European and SAP-oriented contexts.

Source-to-pay adds upstream strategic sourcing - supplier discovery, RFx events, contract negotiation - in front of procure-to-pay. Most mid-market finance teams need P2P; S2P suites are built for dedicated procurement organizations.

An internal request to buy something, submitted before any commitment is made to a vendor. It captures what's needed, why, the estimated cost, and routes for approval - it's the "ask" stage, and intake is the front door that collects it.

A requisition is internal (an employee asking permission); a PO is external (the company committing to a vendor). The requisition authorizes; the PO executes.

A PO is the buyer's document saying "we agree to buy this"; an invoice is the seller's document saying "now pay for it." Matching the two is a core AP control.

Direct procurement buys inputs to the product (raw materials, components); indirect buys everything that runs the business (software, services, supplies, equipment). Finance almost always owns or governs indirect spend; direct typically sits with operations or supply chain.

Operational procurement is the daily transaction flow - requests, POs, receiving. Strategic procurement is category strategy, supplier consolidation, and negotiation. You need operational discipline first; strategy without transaction control is theory.

A model where the CFO organization - controller, VP finance, AP - owns purchasing controls instead of a standalone CPO function. It prioritizes budget control, approval integrity, and clean accounting over sourcing sophistication, and it's the dominant model in the mid-market.

A goods receipt (or goods receipt note) is the record confirming that ordered items actually arrived - what, how much, when, and who confirmed it. It's the third leg of 3-way matching.

Comparing the PO, the receipt, and the invoice before paying, so you only pay for what was ordered and actually received.

Committed spend is money you've promised (approved requests and open POs) but haven't been billed for yet; actual spend is invoiced or paid. Budgets that only show actuals understate how much budget is really gone.

Purchases made outside the approved process - no request, no approval, or off negotiated contracts. It surfaces as surprise invoices and expense-report purchases that should have gone through procurement.

The long tail of low-dollar, infrequent purchases across many vendors - typically a large share of transactions but a small share of total spend, and rarely worth heavy process.

The percentage of total spend that flows through your governed procurement process (managed spend ÷ total addressable spend). Higher is better; it's the headline metric for procurement program maturity.

A PO covering repeated deliveries over a period - with a not-to-exceed amount - so recurring purchases from one vendor don't each need a new PO.

A connection that lets requesters shop a supplier's web catalog (via standards like cXML or OCI) and return the cart into the procurement system as a request or PO, keeping negotiated pricing and approvals intact.

Stampli runs the full procure-to-pay lifecycle in one platform - custom intake forms, configurable approval workflows, budget validation before approval, and multiple fulfillment paths (POs, cards, or service tickets), connected through to invoice matching and payment. The organizing idea is control before commitment: every request starts with budget context, GL coding, and clear approval ownership before money is committed, so finance isn't in cleanup mode later.