SAP GR/IR clearing explained

Where this fits

GR/IR sits between goods receipt and invoice verification. It helps separate the physical receipt event from the supplier invoice event.

How GR/IR works

When a goods receipt (GR) is posted in MIGO, SAP creates an accounting entry that debits the stock or consumption account and credits the GR/IR clearing account. When the invoice is posted in MIRO, SAP debits the GR/IR clearing account and credits the vendor account. If quantities and prices match perfectly, the GR/IR line items net to zero and can be cleared. If they do not match, a balance remains on the GR/IR account until the difference is resolved or written off. The GR/IR account is therefore a temporary suspense account, not a permanent liability.

Common issues

• Goods are received but the invoice has not arrived or cannot be matched.
• Invoice quantity, price, tax, or purchase order reference differs from the receipt evidence.
• Old balances remain because reversals, returns, cancellations, or invoice corrections were not handled consistently.

Common mismatch patterns

• Quantity differences — invoice quantity is higher or lower than the total GR quantity for the PO line. Common with partial deliveries, over-shipments, or returns not updated in SAP.
• Price differences — invoice price differs from the PO net price due to price changes, scales, or unplanned delivery costs added in MIRO.
• Tax differences — tax code or tax amount on the invoice does not match the PO or GR. Often caused by vendor invoice formatting or jurisdiction changes.
• Currency differences — foreign-currency POs create exchange rate variances between GR date and invoice date. The GR/IR account may show a residual in local currency even when foreign currency matches.
• Timing differences — GR posted in one period, invoice posted in another, or month-end closing prevents clearing until the next period.
• Returns and credit memos — a return delivery or credit memo was posted but did not correctly reference the original GR or invoice, leaving unmatched items.

Diagnostic questions

• Which purchase order, goods receipt, and invoice documents are involved?
• Is the mismatch quantity-based, price-based, tax-related, timing-related, or reversal-related?
• Does the open item represent a real business mismatch or a cleanup item?

Where to check

• FBL3N — line items on the GR/IR clearing account. Look for open debits and credits that do not net to zero.
• ME23N — PO history tab shows the full document flow: GRs, invoices, returns, and credit memos per PO line.
• MIGO — review GR documents, movement types, and whether returns were posted correctly.
• MIRO / MIR4 — invoice documents, blocked reasons, and variance details. Check for unplanned delivery costs.
• MR11 — GR/IR maintenance: lists open items and allows write-off of small, approved differences.
• F.13 — automatic clearing program for GR/IR and other clearing accounts. Useful for mass clearing when document assignments match.

Tables and fields

• BSEG — accounting document segment; contains GR/IR account postings with PO reference (EBELN, EBELP).
• BSIS — open items for the GR/IR account; key for FBL3N and reconciliation.
• EKBE — PO history; aggregates GR and invoice references per PO item.
• MKPF — GR document header.
• MSEG — GR document items; links to PO and accounting.
• RBKP — invoice document header.
• RSEG — invoice document items; links to PO and GR.

When to escalate

Escalate when the mismatch indicates a process problem rather than a data cleanup task. Examples: repeated quantity differences from the same vendor suggest a receiving or vendor communication issue; persistent price differences suggest procurement is not updating outline agreements or info records; large old open items with no supporting documents may indicate fraud, theft, or system bypass. Data cleanup (MR11, F.13, manual clearing) should only be done after the root cause is understood and approved by finance.

Retail-specific: month-end close issues

Retail month-end closing faces unique challenges due to high transaction volume, POS reconciliation, markdown accruals, and inventory adjustments.

• GR/IR open items: high-volume retail procurement creates large numbers of unmatched GR/IR lines. Check FBL3N for old items and MR11 for cleanup.
• POS posting status: missing or delayed POS data (WPUUMS IDocs) causes revenue and inventory postings to be incomplete at period end. Check WE02 for failed IDocs.
• Markdown accruals: end-of-season markdowns may require accrual postings that are not yet reflected in the general ledger.
• Inventory adjustment accounts: cycle counts, shrinkage postings, and damage write-offs accumulate in adjustment accounts that must be reviewed before close.
• Timing: retail often operates with tight close windows. GR/IR, POS, and inventory postings that span period boundaries can delay close.

A useful month-end close ticket should include: the period being closed, the specific account or process that is blocked, the volume of open items, and whether the issue is recurring every month-end.