SAP procure-to-pay process map

Where this fits

Use this map when a procurement need exists but the expected purchase order, receipt, invoice, liability, or payment result does not. Procure-to-pay incidents are easiest to resolve when the physical, commercial, and accounting evidence is compared at the same purchase-order item.

Process and evidence flow

1. NeedRequisition or demandQuantity, date, account assignment, specification, and approval need are explicit.
2. OrderPurchase orderSupplier, price, quantity, delivery terms, account assignment, and release status are valid.
3. ReceiveGoods receipt or service acceptancePhysical or service evidence is posted against the intended PO item.
4. VerifySupplier invoicePrice, quantity, tax, reference, and receipt evidence pass the required checks.
5. SettleLiability and paymentThe invoice is released, due, paid, and cleared with the expected accounting result.

Checkpoint-to-evidence map

Transition	Evidence that should exist	Typical reason it stops	Next route
Need → purchase order	Approved requisition or other valid demand, source decision, and complete account assignment.	Missing source, release, budget, master data, contract, or purchasing responsibility.	PO creation diagnostics
Purchase order → receipt	Released PO item with open quantity and delivery or service evidence.	Closed/deleted item, wrong reference, quantity/UoM mismatch, material, batch, quality, or service-entry issue.	Goods receipt diagnostics
Receipt → invoice	PO history showing the applicable goods receipt or accepted service and its quantity/value.	Missing receipt, wrong PO item, partial delivery, return, or GR-based invoice-verification mismatch.	Invoice verification diagnostics
Invoice → liability	Posted invoice document, variance status, tax result, and supplier open item.	Price, quantity, tax, duplicate, tolerance, account, period, or approval issue.	Three-way match diagnostics
Liability → settlement	Due and released supplier item, payment proposal/run, bank result, and clearing document.	Payment block, terms, bank data, payment method, approval, exception, or clearing mismatch.	Payment-run diagnostics

How to trace a stopped P2P process

1. Capture the purchase order and item, supplier, material or service, expected quantity/value, company code, plant, and expected business result.
2. Use purchase-order history to align the order, goods or service receipt, invoice, returns, reversals, and credit memos at item level.
3. Name the failed transition: demand-to-order, order-to-receipt, receipt-to-invoice, invoice-to-liability, or liability-to-payment.
4. Separate a real commercial variance from missing or late evidence. Do not raise tolerance, release an invoice, or clear GR/IR merely to remove a technical symptom.
5. After correction, confirm the downstream result: usable stock or accepted service, correctly posted invoice, expected GR/IR position, and cleared supplier liability.

Evidence to capture before routing

• PO and item, supplier, material/service, quantity and value, account assignment, plant, company code, and document currency.
• Release status, open quantity, delivery-completed/final-invoice indicators, PO history, and exact variance or block.
• Receipt, reversal, return, invoice, credit memo, payment, and clearing document references where they exist.
• Expected business outcome, last correct evidence, and the owner authorized to approve any commercial exception.

Boundaries and non-goals

This map does not assume every procurement path requires a material goods receipt. Services, limits, evaluated receipt settlement, consignment, subcontracting, intercompany, central procurement, and external networks use different evidence. The diagnostic rule remains the same: identify what the next control expects and prove whether that evidence exists.

Official references

• SAP: goods receipts for purchase orders
• SAP: invoice processing
• SAP: invoices for purchase orders and GR/IR
• SAP: goods-receipt-based invoice verification