Author: 0cek2

If you’ve ever sat through a month-end close at a company running SAP or a similar ERP, you’ve met GR/IR. The balance is never zero, it keeps growing, and every month someone asks, “So what is this, exactly?”

I’ll start with the plain-language version, then get into what actually happens on the ground.

So what is GR/IR?

GR/IR stands for Goods Receipt / Invoice Receipt. It’s a clearing account, a waiting room between two events that almost never happen on the same day: the goods (or services) arrive, and the vendor’s invoice arrives.

Why do we need a waiting room?

Because accounting follows the event, not the paperwork. Remember, the accrual method ! Say the goods hit the warehouse on the 28th, but the invoice only shows up on the 5th of next month. The obligation already exists on the 28th, so it has to be on the books in that month.

The journal entries

A simple example. You buy goods worth 100 curr(ency), and the PO is already created.

Neither of the two entries below is a manual journal. SAP posts them by itself, because the accounts were set up beforehand and the system just picks them up when the document is saved.

Step	SAP transaction	Account	Debit (Curr)	Credit (Curr)
1. Goods arrive (Goods Receipt)	MIGO	Inventory (or expense)	100
		GR/IR		100
2. Vendor invoice posted (Invoice Receipt)	MIRO	GR/IR	100
		Accounts Payable		100

So who decides which accounts get hit in the first journal? Nobody at the moment of posting. It’s configured at the start, in Materials Management:

• Stock materials: the valuation class in the material master (MM03, Accounting view) points to the inventory account, through the account determination in OBYC.
• Non-stock items: the account assignment on the PO line decides. A cost center sends it to expense, an asset number sends it to fixed assets, a WBS element sends it to the project.

Account Determination in SAP MM

If everything goes smoothly, GR/IR is back to zero. The two entries cancel each other out.

Life is rarely that smooth.

Why the balance isn’t zero at the end of period

These are the ones I run into most:

• Goods received, invoice not yet in. Normal, and exactly what the account is for. The balance acts like an accrual for liabilities not yet billed.
• Invoice posted, goods not yet received. Usually the warehouse is late posting the GR, or the vendor invoiced before shipping.
• Quantity differences. PO for 100 units, 95 arrive, but the invoice says 100. Or the other way around.
• Price differences. The PO price and the invoice price don’t match, and the difference gets stuck if the configuration isn’t right.
• Partial deliveries. One PO, three deliveries. Miss one GR or one invoice and it never reconciles.
• Services. Services run through service entry sheets. If the approval is late, the work is done but not recorded.
• Blocked or held invoices, reversed GRs, wrong PO references. Each one leaves an open item behind.
• Old items nobody ever cleaned up. The most dangerous kind. Small balances from two or three years ago pile up, and nobody touches them because nobody remembers where they came from.

We’ll discuss more on the above pointers in here.

SAP terms you’ll hear a lot

For those working in SAP, this is the vocabulary that comes up whenever GR/IR is on the table:

Term	What it does
MIGO	Goods receipt posting. Stock goes up, GR/IR is credited.
MIRO	Vendor invoice posting. GR/IR is debited, the payable is created.
3-way match	Matching three documents: PO, goods receipt, and invoice. When all three agree, GR/IR clears.	Further Discussion on 3 Ways Matching
MB5S	Report of GR/IR balances by PO. A good starting point for tracing differences.
F.13	Automatic clearing. Can be used to clear GR/IR items that already match.
MR11	Maintain GR/IR clearing account. Used to deal with leftover quantity or price differences.

Note: configuration differs between companies, so check with your SAP team before running any mass clearing.

Credit balance vs. debit balance

	Credit balance	Debit balance
Situation	GR is bigger than IR	IR is bigger than GR
Meaning	Goods received, invoice not yet in	Invoice posted, goods not yet received
Nature	Accrued liability	Prepayment or goods in transit
Chase	The vendor’s invoice	The goods receipt or delivery

What I check at every close

To me, GR/IR is not an account you read as one total. The total can look reasonable while the contents are a mess, because positive and negative items offset each other.

My routine goes roughly like this:

1. Pull the detail by PO, not by account. In SAP that’s usually the open item report for GR/IR.
2. Age the items: under 30 days, 30 to 90 days, over 90 days, over a year.
3. For the recent ones, check whether the invoice is actually being processed. If yes, fine.
4. For the old ones, ask purchasing and the warehouse. Were the goods really received? Is the PO still active, or should it have been closed?
5. Separate what needs a correction from what only needs time.

Items that will never be invoiced, or were posted wrongly, get cleaned up through a correcting entry or the clearing and write-off process your company’s policy allows. One rule: nothing gets cleared without supporting documents and approval. The auditors will ask.

What it does to the financial statements

A large credit balance in GR/IR is basically liabilities that haven’t been billed yet. Ignore it and there are two risks. First, expenses or inventory can end up overstated or understated. Second, payables and cash flow no longer reflect reality. A debit balance is just as much of a problem, because it means an invoice may have been paid before it was clear the goods arrived.

Wrapping up

GR/IR is actually an honest account. It just shows that something upstream, in purchasing, the warehouse, or invoice processing, isn’t in sync. When the balance keeps growing, the problem is rarely the account itself. It’s how the departments work together.

If you have a GR/IR story or question from your own workplace, leave it in the comments.