Definition
Procure-to-pay, or P2P, is the process linking an approved purchase need to ordering, receipt, invoice processing, and payment. It connects the business's buying activity with the controls used to recognize and settle supplier obligations.
A well-controlled P2P process helps the organization buy what was authorized, confirm what was delivered, and pay according to the applicable terms. Efficient processing matters, but speed alone does not establish that a transaction is commercially correct.
Understand where P2P begins and ends
For this glossary, P2P begins with an approved purchasing need and continues through supplier payment. Strategic sourcing and contract negotiation sit upstream within the broader source-to-pay process.
That boundary does not make the activities independent. P2P needs usable supplier records, current commercial terms, approved buying channels, and clear exception rules from the upstream process.
It also creates evidence for future decisions. Ordering behavior, receipt discrepancies, invoice exceptions, and payment performance can reveal where sourcing assumptions or purchasing controls need attention.
Control the handoffs, not just the individual steps
- Requisition and approval: Confirm the business need, authority, and appropriate buying channel. Approval should occur at the point required by the organization's policy, not be reconstructed after the purchase.
- Purchase order: Translate the approved requirement into accurate supplier, item, quantity, price, and delivery instructions. The purchase order must reflect applicable terms rather than a stale template.
- Receipt or service acceptance: Record what was actually delivered or accepted. Services may require evidence of milestones, deliverables, or authorized acceptance instead of a physical goods receipt.
- Invoice reconciliation: Compare the invoice with the appropriate purchase, contract, and receipt evidence. Route differences according to defined tolerances and approval responsibilities.
- Payment: Pay approved obligations through controlled payment procedures. Preserve separation between supplier maintenance, transaction approval, and payment authority where required.
Each handoff needs a clear owner and a retained audit trail. An unresolved upstream issue should not disappear because a downstream team is under pressure to clear a queue.
What a three-way match does and does not prove
A three-way match compares the invoice, purchase order, and receipt information. It can detect differences in quantities or prices among those records, subject to the system's configuration.
A match does not necessarily prove that the purchase order reflected the negotiated contract. If the wrong price was copied consistently into the order and invoice, matching may confirm consistency while missing the commercial error.
Nor does matching prove that the underlying purchase was necessary or that a supplier was properly qualified. Those decisions require their own controls and evidence.
A hypothetical invoice exception
In the shared component initiative, the agreed price is $9 per individual unit. Each case contains 100 units, so an order for 100 cases should carry a price of $900 per case and a total of $90,000.
Assume the business receives all 100 cases, but the invoice charges $920 per case. The invoice total is $92,000, creating a $2,000 difference from the applicable price.
| Control situation | What the team should see |
|---|---|
| Purchase order correctly states $900 per case | The invoice has a $2,000 price exception |
| Purchase order incorrectly states $920 per case | A quantity and price match may pass despite the contract error |
| Pack quantity is missing or wrong | The unit-price comparison itself needs validation |
| Supplier later issues a credit | The credit must be connected to the original exception |
The appropriate response is to verify the contract and transaction facts, resolve the discrepancy, and retain the decision trail. Increasing the purchase-order price merely to clear the invoice would conceal the issue rather than resolve it.
In the shared retrospective example, the full $92,000 remains recorded and no credit has been received. The $2,000 is therefore still an open variance, not recovered cash or an additional realized benefit.
Design exceptions deliberately
Different purchase types may require different matching and acceptance controls. A low-value recurring charge, a complex service milestone, and a physical inventory receipt should not automatically follow identical rules.
Define tolerances with regard to exposure and policy, then monitor their cumulative effect. A small permitted difference repeated across many transactions can become material even when each individual invoice appears routine.
Exception handling should identify the root cause as well as resolve the current transaction. Repeated price mismatches may originate in contract setup, catalog maintenance, unit conversion, or supplier billing, each requiring a different owner.
Measure control quality alongside cycle time
Useful measures include compliant buying-channel use, accurate first-time orders, aged unmatched receipts, recurring price exceptions, duplicate-payment findings, and unresolved supplier credits. Interpret these with transaction volume and value, not only a count of processed invoices.
Do not improve payment metrics by suppressing exceptions or making unsupported receipts. Payment timing should follow agreed terms and policy rather than arbitrary delay presented as procurement savings.
Frequently asked questions
- Are P2P and accounts payable the same? No. Accounts payable is part of the broader flow; P2P also includes purchasing authorization, ordering, and receipt or acceptance.
- Does every invoice require a three-way match? Not necessarily. The appropriate control depends on the purchase type, policy, available evidence, and configured workflow.
- Is an avoided overpayment the same as a recovered credit? No. Preventing an incorrect payment, identifying an open variance, and receiving a credit are distinct events and should be reported separately.
Make negotiated terms survive the transaction
VPP connects purchasing controls to the commercial decisions they are intended to enforce. The objective is a traceable path from approved terms to correct transactions, with exceptions resolved rather than hidden in processing statistics.