GR/IR explained with real documents: why buying something posts nothing to your P&L
Buying 6,700 KRW of pork and wrappers produced four documents, two accounting entries, and zero effect on the profit and loss statement. That surprises people the first time they trace it, and the reason it works that way is the single most useful thing to understand about procurement in SAP.
Below is the actual relay, with the real document numbers from a dumpling factory I built from an empty S/4HANA client.
Four documents, but only two of them are accounting
| # | Document | What it claims | Accounting entry |
|---|---|---|---|
| 1 | Requisition · ME51N EBAN 0199000553 |
“we want this” — internal only | none |
| 2 | Purchase order · ME21N EKKO 4500006934 |
a promise to the vendor | none |
| 3 | Goods receipt · MIGO 101 MSEG 5000006252 |
“it physically arrived” | Dr 1050 raw material Cr 9010 GR/IR |
| 4 | Invoice receipt · MIRO RBKP 5100004739 |
“the vendor billed us” | Dr 9010 GR/IR + input tax Cr 2010 accounts payable |
Documents 1 and 2 are intentions. SAP posts nothing for an intention, because wanting a thing and promising to pay for a thing do not change what you own. Documents 3 and 4 are facts, and facts post in pairs.
Why there has to be an account in the middle
The two facts are independent. The truck can arrive on Monday and the invoice on the following Friday — or the invoice can arrive first. Whichever comes first leaves the books temporarily lopsided:
- Goods arrived but no invoice yet: you own inventory you have not been billed for.
- Invoice arrived but no goods yet: you owe money for something not on your shelves.
The GR/IR clearing account is where that asymmetry is parked so both sides of the books stay balanced in the meantime. In this build the account is 9010 (there is a whole 9010–9090 band, one per stock class, so raw materials and packaging clear separately). The lifecycle of a single purchase looks like this:
That zero is the whole point. A GR/IR account that clears to zero is a procurement process telling you it is internally consistent. Which is also why the balance that doesn't clear is one of the most useful diagnostics in the system.
Reading a GR/IR balance that won't go away
Old open items on GR/IR are almost never an accounting problem; they are a logistics problem that accounting has faithfully recorded. The residue tells you which:
| What is sitting there | What actually happened |
|---|---|
| Credit balance (goods > invoice) | delivered but never billed — a missing vendor invoice, or one stuck in a block |
| Debit balance (invoice > goods) | billed but not delivered, or delivered short and never corrected |
| Small residual per line | quantity matched, price didn't — the difference went to price variance, the rounding stayed |
Useful places to look: MB5S for GR/IR balances by purchase order, ME2N/ME2L for the order-side view, and FBL3N on the clearing account itself when you want the accounting line items with their document trail.
The part that surprises accountants
Add up the P&L effect of the entire purchasing phase — five transactions, 6,700 of raw material, 7,480 of payables including tax:
zero
Buying does not make you poorer. It converts one asset (a future payment) into another asset (pork). Your balance sheet changes shape; your income statement does not move at all. Expense begins later, at the moment the material is issued to production — and even then it is not really expense yet, it is value moving into work in process.
This is worth internalizing because it explains a category of question that otherwise sounds unanswerable: “we bought a lot this month, why didn't costs go up?” They didn't go up because you haven't used anything yet. The system is not hiding the cost; it is refusing to recognize it early.
The short version
- Intentions (PR, PO) post nothing. Facts (GR, IV) post in pairs.
- GR/IR exists because the two facts arrive at different times, and the books have to balance in between.
- Clearing to zero is the three-way match confirming itself.
- An aged GR/IR balance is a logistics story, and the sign of the balance tells you which story.
- Procurement never touches the P&L. Consumption does.
These document numbers come from a complete build of one small company in S/4HANA — 238 configuration steps, 20 master records, 31 transactions, followed by a full month-end close. It is written up as two books: a business novel for people meeting SAP for the first time, and a technical build record with every posting, table and account determination attached.
Transactions referenced: ME51N, ME21N, MIGO (101), MIRO, MB5S, ME2N, FBL3N. Accounts shown (1050 raw materials, 9010 GR/IR, 2010 payables) are from this build's chart of accounts; yours will differ, but the shape of the entry will not.
New: a free 16-page sample of the novel — the prologue, Chapter 1 and the scene where 6,700 won of raw material disappears from the balance sheet. No email required.
Comments
Post a Comment