FICO Accounts Payable Part 7: GR/IR Clearing Account — Why It Doesn't Clear and How to Fix It
Full lesson currently free to read · AI practice limits apply separately
Master the GR/IR clearing account: how goods receipts and invoices offset each other, why balances remain (quantity and price differences, missing invoices or receipts), how to analyse them per purchase order, and how MR11 and regrouping are used at month end.
Visual overview
Explanation
📌 KEY POINTS
✅ Goods receipt credits GR/IR; invoice receipt debits it — when both match, the purchase order item nets to zero.
✅ Balances remain when quantities or values differ, or when one side hasn't been posted yet.
✅ Analysis is done per purchase order item, comparing GR and IR quantities and values.
✅ MR11 clears differences that will not be resolved, for example when no further invoice will come.
⚠️ Writing off GR/IR balances without analysis hides missing invoices and supplier disputes.
━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
This part tackles one of the most common month-end problems in FICO.
━━━━━━━━━━━━━━━━━━━━
▶ 1. HOW GR/IR WORKS
When goods are received against a purchase order, inventory or expense is debited and GR/IR is credited at the PO price. When the invoice arrives, GR/IR is debited and the vendor credited. If quantity and price match, the PO item's GR/IR balance is zero. The account therefore shows goods received not yet invoiced (credit) and invoiced not yet received (debit).
━━━━━━━━━━━━━━━━━━━━
▶ 2. WHY IT DOESN'T CLEAR
Common reasons: partial deliveries invoiced fully, invoices with quantity differences, price differences handled outside the invoice, invoices posted to the wrong PO item, returns posted only on one side, or receipts and invoices simply waiting for each other. Each leaves a residual per PO item.
━━━━━━━━━━━━━━━━━━━━
▶ 3. ANALYSING BALANCES
Report GR/IR balances by purchase order item with GR and IR quantities and values, and age them. In S/4HANA, Fiori apps for GR/IR reconciliation help assign responsibility and track resolution. Large old balances usually need purchasing or the supplier to act, not finance.
━━━━━━━━━━━━━━━━━━━━
▶ 4. CLEARING WITH MR11
When a difference will not be resolved — the supplier will not invoice the remaining quantity, or a small price difference is accepted — MR11 clears the PO item's GR/IR balance, posting the difference to a price difference or expense account. It should be used with tolerances and approval, not as a blanket write-off.
━━━━━━━━━━━━━━━━━━━━
▶ 5. MONTH-END PRESENTATION
At period end, balances may be regrouped (classic program F.19) so that goods received but not invoiced show as a liability and invoices without receipt as an asset in the balance sheet, rather than netting in one account. Reconciliation with purchasing and accrual decisions also happens here.
━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP
- Report GR/IR balances by PO item for one company code.
- Pick three uncleared items and identify the cause of each.
- Clear one test difference with MR11 within tolerance.
- Set up a monthly GR/IR review with purchasing.
✅ CHECKPOINT: every material GR/IR balance has a cause, owner and planned action.
How the SAP process fits together
SAP PROCESS EXPLORER · Finance: post to report
ERPClimb.comAccounts Payable — process breakdown
Topic-specific conceptual flow: how key objects and decisions fit together. SAP configurations and exceptional cases can follow different paths.
Selected process stage
Invoice
Enter supplier invoice and liabilities
What this specific lesson teaches
Master the GR/IR clearing account: how goods receipts and invoices offset each other, why balances remain (quantity and price differences, missing invoices or receipts), how to analyse them per purchase order, and how MR11 and regrouping are used at month end.
Key lesson principle: Goods receipt credits GR/IR; invoice receipt debits it — when both match, the purchase order item nets to zero.
Representative SAP learning flow, not a guarantee of system runtime sequence in every scenario. The chapter-specific facts come from the published lesson text.
Real project scenario
A company's GR/IR balance grew every month. Analysis showed thousands of PO items with goods received but no invoice, mostly from a supplier that sent consolidated monthly invoices posted to one PO line. Invoice entry was changed to assign lines correctly, and old items were cleared after confirming with the supplier.
Common mistakes
- Blanket write-offs of GR/IR balances.
- Analysing only the account total.
- No involvement of purchasing.
- Invoices posted to wrong PO items.
Best practices
- PO-item-level analysis with ageing.
- MR11 within tolerances and approval.
- Monthly review with purchasing.
- Training on correct invoice-to-PO assignment.
Interview angle
Interviewers often ask 'Why does GR/IR not clear and what do you do?' — answer with mechanics, causes per PO item, MR11 and the month-end view.
Frequently asked questions
Why does the GR/IR account not clear in SAP?
Common causes are partial deliveries invoiced fully, invoices with quantity differences, price differences handled outside the invoice, invoices posted to the wrong PO item, returns posted only on one side, or receipts and invoices still waiting for each other. Each leaves a residual per PO item.
When should MR11 be used?
When a difference will not be resolved — the supplier will not invoice the remaining quantity, or a small price difference is accepted. MR11 clears the PO item's GR/IR balance to a price difference or expense account, and should be used with tolerances and approval, not as a blanket write-off.
What happens to GR/IR balances at month end?
Balances may be regrouped, classically with F.19, so goods received but not invoiced show as a liability and invoices without receipt as an asset, rather than netting in one account.
Practice this lesson
Quick check
0 of 3 questions attempted
1. What does a credit balance on a PO item in GR/IR usually mean?
2. When is MR11 appropriate?
3. Why are GR/IR balances regrouped at period end?
Check before use: lesson examples are educational, not a guarantee of correctness for your SAP edition or release. Sample code has not been executed on your SAP system. Confirm API availability, syntax, authorizations and business impact in an approved development or test environment.
More lessons in this topic
- FICO Accounts Payable Part 1: What AP Does and How It Connects
- FICO Accounts Payable Part 2: Supplier Master Data and Core AP Configuration
- FICO Accounts Payable Part 3: Invoice Posting, Payment Terms and Three-Way Match
- FICO Accounts Payable Part 4: Enterprise AP Architecture, Migration and Governance
- FICO Accounts Payable Part 5: Automatic Payment Program Configuration and Payment Runs
- FICO Accounts Payable Part 6: Down Payments, Special G/L Transactions and Clearing