SAP GR/IR Mismatch: Why the Clearing Account Will Not Balance

Most of the balance on a healthy GR/IR account at any month end is legitimate: goods arrived near the period boundary and the invoice will land in the next few days, or an invoice arrived first for a shipment still in transit. These clear by themselves. The practical task is to age the balance and agree a threshold with finance below which no action is taken, so that effort goes to the genuinely stuck items instead of to the whole list every month.

A purchase order line receipted at 95 units and invoiced at 100, or receipted twice and invoiced once, leaves a quantity difference that will persist until either the missing document is posted or the line is written off. Read the item history in ME23N, or EKBE directly, and lay the movement types and invoice documents side by side — the sequence usually explains itself immediately, including the reversal someone posted and forgot to re-post.

When the PO price is changed after the goods receipt, the receipt sits at the old value and the invoice comes in at the new one. Quantities agree perfectly and the account still will not balance, which is what makes this case confusing at first sight. Check the price history on the PO item and the conditions applied at each event. Unplanned delivery costs and freight conditions invoiced separately produce the same pattern.

A GR/IR account that receives direct FI postings will never reconcile against purchasing documents, because part of the balance has no purchasing document behind it. Run FBL3N and look at document types: anything that is not the standard goods receipt or invoice type deserves an explanation. The long-term fix is to block manual posting on the account rather than to clean it repeatedly.

1. Run MB5S for the plant or company code and export the list. This gives quantity and value differences per purchase order line, which is the only view where the two sides sit together.
2. Reconcile the total against the GL balance in FBL3N or FAGLB03. A gap between the two means manual postings exist and must be handled separately.
3. Age the MB5S list by goods receipt date. Split it into recent timing differences and items older than the agreed threshold.
4. For each old item, open the PO history in ME23N or query EKBE and classify it: missing invoice, missing receipt, quantity difference or value difference.
5. Confirm with purchasing whether the missing document is still expected. A PO with the delivery completed indicator set and no further invoice expected is a write-off candidate, not a chase.
6. Check that the invoice is not simply blocked. MRBR shows blocked invoices that will clear the balance as soon as the block is released, and releasing is cheaper than writing off.

Post the missing document where one is genuinely due: the receipt in MIGO, the invoice in MIRO, or the release in MRBR. Where no further document will arrive, use MR11 to maintain the GR/IR clearing account for that purchase order line. MR11 posts the difference to the expense or price difference account driven by your account determination and marks the line as cleared, which is why it must be run with finance agreement and within an open period.

Keep automatic clearing in F.13 for the routine case where a receipt and an invoice match exactly and simply have not been offset. Do not use it as a way to make an unexplained balance disappear. Close the loop by fixing what created the item — a tolerance setting, a missing delivery completed flag, or a receipt step that the warehouse consistently skips.

Escalate to finance before any write-off: MR11 changes reported expense and is their decision, not support's. Escalate to purchasing when the pattern points at process rather than data, for example a supplier who consistently invoices before delivering. Escalate to development when the account determination itself resolves to the wrong account for a specific valuation class, since that is configuration or an enhancement rather than a transactional error, and every future posting will repeat it.

Paste your MB5S line detail into the ERPClimb AI Debugger to get a classification and a clearing path for each open item.

• IDoc status 51 application errors — for invoices that never posted because the inbound IDoc failed.
• Pricing procedure not determined — the sales-side equivalent of a value that will not compute.
• SAP fresher salary in India 2026 — GR/IR reasoning is one of the checks that separates MM offers.