Functionalbeginner
Materials Management (MM): Procure-to-Pay Cycle
The end-to-end process from purchase requisition through goods receipt to invoice verification in SAP MM.
Procure-to-pay is the process of buying something: asking for it, ordering it, receiving it, and paying for it. In SAP each of those steps is a document, and each document refers to the one before.
The GR/IR account is like a temporary escrow holding pen - goods arrive and get counted (GR) before the bill (invoice) shows up, so the system parks the expected cost there until the invoice finally arrives and the two are matched and cleared together, like reconciling a delivery receipt against the invoice that follows days later.
Key Concepts
1
purchase requisition ME51N "we need 100 units"
|
purchase order ME21N "vendor X will supply them at this price"
|
goods receipt MIGO "they arrived"
|
invoice verification MIRO "the vendor billed us; pay it"2
The purchase order is where the money is decided. It states material, quantity, price and delivery
terms, and it carries an account assignment — cost centre, internal order, or nothing at all for stock
items — which determines the accounts that are hit later.
3
Goods receipt creates an accounting document too. Receiving stock is not just a quantity change:
4
debit inventory 10,000
credit GR/IR clearing 10,0005
The GR/IR account is the part worth understanding properly. GR/IR means goods receipt / invoice
receipt, and it exists because goods and invoices arrive at different times.
6
At goods receipt you know the stock arrived but you do not have a bill, so you cannot credit the vendor
yet. The GR/IR account holds the obligation in between.
7
When the invoice comes in:
8
debit GR/IR clearing 10,000
credit vendor payable 10,0009
GR/IR nets to zero and the debt is now properly owed to the vendor. A line stuck in GR/IR means one half
happened and the other did not — goods received and never invoiced, or invoiced and never received.
10
MB5S lists those open balances, and clearing them is standard period-end work.
MB5S
11
The three-way match. MIRO checks the invoice against the purchase order and the goods receipt:
MIRO
12
PO says 100 units @ 100
GR says 100 units received
invoice says 100 units @ 105 <- price difference13
Differences within configured tolerance post through. Outside tolerance, the invoice is blocked for
payment and somebody must release it. That block is a control, not a malfunction — it is what stops
overbilling being paid automatically.
14
Valuation changes the posting. For a material with a standard price, stock is always valued at that
price, and any difference between it and the actual purchase price goes to a price difference account. For
a moving average price, the material's own value is adjusted by each receipt.
15
So the same purchase produces different postings depending on the material's price control — which is why
that setting comes up whenever accounting queries an inventory value.
16
What an interviewer is checking. Not the transaction codes. That you know each document refers to its
predecessor, why GR/IR exists, and what a blocked invoice means. A candidate who can draw the flow and say
what is posted at each step understands the process; one who lists transaction codes has memorised a
screen.
17
What the interviewer is probing.1. "Walk through the procure-to-pay cycle." Probing: end-to-end understanding. Stalls: "You
raise a PO." Moves up: requisition, release, purchase order, goods receipt, invoice receipt,
three-way match, payment — with the document flow linking them.
18
2. "What is the three-way match?" Probing: the control. Stalls: "Checking invoices." *Moves
up:* PO, goods receipt and invoice must agree on quantity and price, with tolerances — this is the
core financial control in purchasing.
19
3. "What happens in accounting at goods receipt?" Probing: the integration point. Stalls:
"Nothing." Moves up: stock is debited and a GR/IR clearing account credited, which is cleared at
invoice receipt — this is where MM meets FI.
20
4. "What is a common cause of a blocked invoice?" Probing: practical experience. Stalls: "A
system error." Moves up: a quantity or price variance outside tolerance, or a missing goods
receipt — resolved in MRBR after correcting the mismatch.