Procure-to-Pay: Requisition to Payment
The full purchasing cycle: purchase requisition, purchase order, goods receipt (101), invoice receipt with three-way match, and payment.
Educational content. SAP behaviour varies by configuration and release. Spotted something off? Report it.
Digital twin
01Purchase requisition
A requisition for 100 EA RM-1000 is created (manually or by MRP).
Business scenario
Production planning needs 100 EA of RM-1000. A requisition becomes a PO to Demo Supplier Ltd.; the goods are received, the invoice is verified and the supplier is paid.
All companies, numbers and documents are fictional demo data.
Step-by-step flow
- 01
Purchase requisition open in twin
A requisition for 100 EA RM-1000 is created (manually or by MRP).
Requisitions separate the need from the purchasing decision; release strategies can require approval.
- 02
Purchase order open in twin
The buyer converts the requisition into PO 4500001234 and sends it to the supplier.
The PO fixes price, quantity, delivery date and terms — the basis for GR and invoice matching.
- 03
Supplier delivers open in twin
The supplier ships; the truck arrives at the receiving dock.
Nothing posts until goods receipt.
- 04
Goods receipt (101) open in twin
Stock rises 500 → 600 EA; material document 5000123456; Dr Inventory / Cr GR/IR.
See the 101 digital twin for every detail.
- 05
Supplier invoice arrives open in twin
Invoice DS/2026/0456 for ₹1,00,000 arrives. Check it against PO and GR.
Invoice verification compares PO price, GR quantity and invoice amount. Tolerances are configuration dependent.
- 06
Post invoice in MIRO open in twin
GR/IR is cleared and a payable to the supplier is created.
It turns the GR/IR liability into a payable with due date and payment terms.
- 07
Payment run open in twin
The automatic payment run pays the due invoice.
Procure-to-pay ends in FI accounts payable.
- 08
Procure-to-pay complete open in twin
PR → PO → GR → Invoice → Payment. GR/IR is balanced at zero for this PO item.
Every document references its predecessor — the document flow you can inspect below.
- 09
Invoice blocked for payment open in twin
₹1,20,000 vs expected ₹1,00,000: the invoice posts but is blocked for payment until the variance is resolved.
Tolerance limits (configuration dependent) decide whether the invoice is blocked or cannot be posted.
SAP documents
Stock impact
| Step | Plant / SLoc | Stock type | MvT | Change |
|---|---|---|---|---|
| Goods receipt (101) | 1000 / 0001 | Unrestricted use | 101 | +100 EA |
Accounting impact
Valuated goods receipt
TypicalGoods receipt (101)
- Dr Inventory (stock account) (BSX)₹1,00,000
- Cr GR/IR clearing (WRX)₹1,00,000
Inventory up; GR/IR clearing holds the liability until the invoice arrives.
Invoice receipt matching the goods receipt
TypicalPost invoice in MIRO
- Dr GR/IR clearing (WRX)₹1,00,000
- Cr Supplier (accounts payable)₹1,00,000
GR/IR is debited, clearing the GR credit; the supplier account is credited. Input tax lines (e.g. GST) are omitted — configuration dependent.
Outgoing payment (FI)
ConceptualPayment run
- Dr Supplier (accounts payable)₹1,00,000
- Cr Bank₹1,00,000
Payment is an FI process. Bank clearing accounts and house banks depend on configuration.
Typical conceptual flow. Actual G/L accounts and posting behaviour depend on material valuation, automatic account determination and system configuration.
Movement type
- 101GR for POReversal: 102
End-to-end purchasing of stock material from need to supplier payment.
Transactions & Fiori apps
- ME51N — Create PR
- ME21N — Create PO
- MIGO — Goods Receipt
- MIRO — Enter Incoming Invoice
- MRBR — Release Blocked Invoices
- F110 — Automatic Payment Run (FI)
- Manage Purchase Requisitions
- Manage Purchase Orders
- Post Goods Receipt for Purchasing Document
- Create Supplier Invoice
- Manage Supplier Invoices
Differences by SAP version
Flexible workflow replaces classic release strategies for many purchasing documents — validate per scope.
Configuration
Release strategies
Configuration dependentPR/PO approval rules.
Invoice tolerances
Configuration dependentPrice/quantity variance limits per company code.
GR-based invoice verification
Configuration dependentControls whether invoices match per GR.
Prerequisites
- Material, supplier and info record master data
- Release strategy (if used)
- Tolerance groups for invoice verification
Master data
- Supplier / business partner
- Purchasing and payment data.
- Purchasing info record
- Price and conditions.
- Material master
- Purchasing and accounting views.
Organizational structure
- Company code 1000
- Purchasing org 1000
- Plant 1000
Tables
| Table | Description |
|---|---|
| EBAN | Purchase requisition |
| EKKO / EKPO | PO |
| EKBE | PO history |
| RBKP / RSEG | Invoice |
| BSIK / BSAK | Supplier open/cleared items (ECC; views in S/4HANA) |
Integration
- FIGR/IR, accounts payable, payment.
- COAccount-assigned purchases.
Common errors
“Invoice blocked for payment”
Likely causes: Price or quantity variance beyond tolerance; Invoice before GR with GR-based IV
Where to look: MRBR · Tolerance settings
Troubleshooting
Something went wrong? Work through these checks in order. They are diagnostic questions, not configuration instructions — confirm changes with your system owner.
CHECK 1
Release
- Is the PR/PO released?
CHECK 2
Invoice
- Are variances within tolerance?
- Has the GR been posted (GR-based IV)?
Interview questions
Explain the P2P cycle with documents.
PR → PO → GR (material and accounting document) → invoice (MIRO, invoice and accounting document) → payment (FI). Each references the previous document.
What is three-way match?
Matching PO price/terms, GR quantity and invoice amount before the invoice is released for payment.
Quiz
References
- SAP SE — SAP Help Portal: Procurement — Purchase Order Processing (source)
- SAP SE — SAP Help Portal: Logistics Invoice Verification (source)
Explanations are original. They summarize standard behaviour; always validate against your system's release and configuration.
Version history
| Version | Change |
|---|---|
| 1.0.0 | Initial version. |