Procure-to-Pay (P2P) is the end-to-end transactional process used to request, order, receive, invoice and pay for goods or services. A well-controlled P2P process gives an organization visibility over what is being bought, who approved it, whether it was received, whether the invoice is correct and whether payment is due.
SAP describes the P2P flow as beginning with a purchase requisition and continuing through purchase order creation, supplier fulfilment, receipt or service entry, invoice reconciliation and payment.
Procure-to-Pay Process at a Glance
Need → Purchase Requisition → Approval → Source / Contract Check → Purchase Order → Supplier Confirmation → Delivery / Service → Goods Receipt or Service Entry → Invoice → Match / Reconcile → Payment Approval → Payment → Reconciliation
P2P vs Procurement vs Source-to-Pay
| Process | Main Scope |
|---|---|
| Procurement | Broad commercial lifecycle including strategy, sourcing, contracting, buying and supplier management |
| Procure-to-Pay (P2P) | Transactional flow from request/requisition through ordering, receiving, invoice processing and payment |
| Source-to-Pay (S2P) | Broader process that normally includes sourcing and contracting before the P2P transaction |
1. Identify the Requirement
The process begins when the business needs a product or service. Good P2P control starts before the PO: the requirement should be clear enough to identify the correct item or service, quantity, specification, delivery date, cost centre/project and business justification.
2. Create the Purchase Requisition
A purchase requisition (PR) is an internal request to buy. It is not the same as the purchase order sent to a supplier. SAP identifies the PR as the first transactional step in the P2P flow.
The requisition commonly captures the requester, item/service, quantity, estimated value, account assignment, required date and suggested supplier or contract where applicable.
3. Approval
The requisition is routed according to the organization’s delegation of authority, budget rules, category controls and approval workflow. High-value, sensitive or non-standard purchases may need additional approval.
4. Source or Contract Check
If an approved supplier and contract already exist, the transaction may move directly to PO creation. If no suitable source exists, the requirement may need a sourcing event, quotation exercise or supplier qualification before a PO can be issued.
5. Purchase Order Creation
Once the requisition is approved, one or more purchase orders may be created and sent to the supplier. The PO should accurately reflect the commercial agreement, including description, quantity, price, delivery terms, tax treatment, Incoterm where relevant and other conditions.
6. Supplier Confirmation and Fulfilment
The supplier confirms the order and delivers the goods or performs the service. Confirmation is operationally important because it can reveal quantity, price or delivery-date differences before they become receipt or invoice exceptions.
7. Goods Receipt or Service Entry
Goods received should be recorded against the PO. For services, an approved service entry or equivalent confirmation may be required. SAP supports both receipts and service entry sheets as evidence that the ordered goods or services have been delivered.
Late or inaccurate receipt posting is one of the most common reasons otherwise-correct invoices remain blocked.
8. Invoice Processing and Matching
The supplier invoice is compared with the purchasing and receiving records. Depending on the organization and purchase type, this may use:
- 2-way match: invoice against PO or contract.
- 3-way match: invoice against PO and goods receipt/service entry.
SAP Ariba supports configurable 2-way and 3-way invoice matching and routes discrepancies for reconciliation or exception handling.
Worked P2P Example
A PO is issued for 1,000 cartons at BHD 2.000 each, so the PO value is BHD 2,000.
The warehouse records a receipt for only 900 cartons, but the supplier invoices the full 1,000 cartons.
A 3-way match should identify the quantity mismatch. The invoice should not simply be approved because the PO value is correct. The missing receipt, short delivery, over-invoice or outstanding quantity must be resolved according to the commercial agreement and tolerance rules.
Key P2P Controls
- Supplier master controls: controlled creation and change of supplier and bank details.
- Delegation of authority: approval limits aligned with purchase value and risk.
- Segregation of duties: avoid one person controlling requisition, approval, receipt and payment.
- No-PO / no-pay policy: where suitable, require an approved PO before suppliers invoice.
- Contract and price controls: ensure PO pricing reflects approved commercial terms.
- Receipt discipline: record goods or services promptly and accurately.
- Duplicate invoice checks: prevent duplicate payment.
- Matching tolerances: define acceptable quantity/price differences and route material exceptions.
- Blocked-invoice management: assign ownership and ageing targets.
- Open-PO reconciliation: review old commitments, unmatched receipts and invoices regularly.
Common P2P Failure Points
| Failure | Likely Result | Improvement |
|---|---|---|
| PO created after invoice | Weak spend control and retrospective approval | Improve requisition compliance and emergency-buy procedure |
| Wrong PO price | Invoice exception | Contract/price master governance |
| Receipt not posted | Invoice blocked | Receipt reminders and owner accountability |
| Supplier invoices wrong quantity | Mismatch and payment delay | Confirmation and invoice validation |
| Duplicate invoice | Overpayment risk | System duplicate checks |
| Old open POs | Incorrect commitments and reporting | Regular PO ageing and closure |
Useful P2P KPIs
- PR-to-PO cycle time
- Approval cycle time
- PO compliance / maverick-spend rate
- Supplier confirmation time
- Receipt-posting timeliness
- First-pass invoice match rate
- Blocked invoice percentage and ageing
- Invoice processing cycle time
- On-time payment rate
- Early-payment discount capture
- Open PO / commitment ageing
Interview Question: Explain the P2P Process
A strong answer is: P2P starts with a business requirement and purchase requisition, followed by approval, PO creation, supplier fulfilment, receipt or service entry, invoice matching and exception resolution, then payment. The key controls are approval authority, segregation of duties, accurate PO and receipt data, invoice matching and supplier-master governance.
Related SCMANA Guides
References
- SAP Learning, Define the Purchase Order Lifecycle
- SAP Learning, Explaining the Invoice Reconciliation Process
Download the Practical Workbook
Use the SCMANA P2P KPI Calculator to calculate PO cycle, invoice match, exception and other procure-to-pay KPIs.
Comments 1