GR/IR Clearing in S/4HANA: How to Keep the Account Clean at Month-End
GR/IR clearing in SAP S/4HANA: why balances grow, how to use F.13, MR11 and regrouping, and a month-end routine that keeps the account clean.

The GR/IR clearing account is one of the most honest accounts in SAP S/4HANA. It tells you, every single day, whether purchasing, receiving and accounts payable are telling the same story. When the balance grows quietly month after month, it is rarely a configuration bug. It is usually a process signal that nobody owns.
This article explains how GR/IR works in S/4HANA, why balances pile up, and a practical routine to keep the account clean at month-end: automatic clearing, write-offs with MR11, regrouping for the balance sheet, and the Fiori monitor that gives each open item an owner.
What the GR/IR clearing account actually does
In a standard purchase-to-pay flow with three-way match, two postings meet on the GR/IR account:
- Goods receipt (MIGO): debit inventory or expense, credit GR/IR. In automatic account determination this is transaction key WRX in OBYC.
- Invoice receipt (MIRO): debit GR/IR, credit the supplier. Differences are handled according to your valuation and tolerance settings, for example price differences posting to a price-difference account for materials at standard price.
When quantity and value of goods receipts and invoices match for the same purchase order item, the GR/IR balance for that item nets to zero. The account is open-item managed, so the matching items still need to be cleared to disappear from the open-item list. That clearing step is where many companies fall behind.
Why GR/IR balances keep growing
In most finance reviews, the same root causes appear:
- Goods received, invoice never posted. The supplier invoices late, sends the invoice to the wrong address, or the invoice is blocked and nobody follows up.
- Invoice posted, goods never received. The receiving step is skipped for services or for urgent deliveries, so AP posts the invoice but the GR never arrives.
- Quantity differences. Partial deliveries, over-deliveries, and returns that are not mirrored by credit memos.
- Small value differences. Rounding, exchange-rate effects and freight lines that leave cents or a few dollars open per item.
- Closed or old purchase orders. Items from last year that are economically finished but still open on the account.
- No automatic clearing job. Balanced items stay open simply because no one runs clearing.
The consequence is not only cosmetic. A noisy GR/IR account hides real accrual exposure, makes the balance sheet harder to explain to auditors, and slows month-end close because people reconcile by spreadsheet.
What changes in S/4HANA
The logic of GR/IR is the same as in ECC, but three things make it easier to manage in S/4HANA:
- Universal Journal (ACDOCA). GR/IR line items live in the same table as every other financial posting, with the purchasing reference available for analysis. You can analyze balances by purchase order, supplier, plant or profit center without building a separate extract.
- Fiori monitoring. The app Monitor GR/IR Account Balances lists open purchase order items with GR/IR differences and lets you assign a responsible person, set a processing status and record notes. Depending on edition and release, it can also propose likely root causes. Check what is active in your system before promising it to users.
- Regrouping in the new general ledger logic. The classic regrouping program F.19 belongs to the classic GL world. In S/4HANA, GR/IR regrouping for the balance sheet is typically handled through FAGLF101 (balance sheet supplement / reclassification) with the corresponding configuration. Confirm the exact setup on your release with your system and SAP documentation.
On the baseline I use for these articles, SAP S/4HANA Cloud Private Edition / SAP Cloud ERP Private on the latest feature pack and on-premise on the same level, all of these tools are available. In SAP Cloud ERP (Public Edition) the Fiori apps are the main route and some classic transactions are not exposed.
Step 1: Configure and schedule automatic clearing (F.13 / SAPF124)
Automatic clearing is the cheapest win. Items that already net to zero should not need a human.
- Clearing criteria (OB74). For the GR/IR account range, use the purchasing document and item (EBELN, EBELP) as grouping criteria. This keeps clearing at the level where the business logic lives.
- GR/IR special processing. When you run F.13, activate the GR/IR account special processing option so the program groups items by purchase order item.
- Test first. Run in test mode, review the clearing proposal and the log, then run productively.
- Schedule it. Create a periodic background job (weekly is common, plus one run before close) using program SAPF124 with a saved variant.
- Tolerances. If small differences should be cleared automatically, align tolerance groups for GL accounts (OBA0) with your policy and document who approved the threshold.
Step 2: Clean residual differences with MR11
Some items will never match on their own: the supplier will not send a final invoice, or the remaining quantity will never arrive. MR11 (Maintain GR/IR Clearing Account) writes off these differences and closes the purchase order items in the process.
Good practice for MR11:
- Use selection by purchase order age and difference amount, not only by supplier.
- Run it first in simulation, export the list, and get purchasing confirmation for larger items.
- Agree a policy: who approves write-offs, which threshold applies, and which account receives the offset.
- Remember that MR11 postings can be displayed and reversed with MR11SHOW if a decision was wrong.
MR11 is not a substitute for chasing missing invoices. It is the last step after purchasing and AP have confirmed that nothing else will arrive.
Step 3: Regroup GR/IR for the balance sheet
At period end, the GR/IR account is a mix of two very different positions:
- Goods delivered but not invoiced: a liability (an accrual for invoices still to come).
- Goods invoiced but not delivered: an asset (closer to a prepayment).
Netting them hides both. Regrouping reclassifies the net balance per purchase order item to adjustment accounts, so the balance sheet shows each position on the correct side. The postings are typically reversed at the start of the next period. Agree the account mapping with your external reporting team and keep the regrouping log with your close documentation.
Step 4: Give every open item an owner
Technology clears the easy items. The hard ones need people. A simple operating model works well:
- Weekly: automatic clearing job runs; the monitor shows the remaining exceptions.
- Assignment: items older than an agreed age are assigned to buyers or receiving owners in Monitor GR/IR Account Balances, with a status and a short note.
- Before close: AP reviews blocked invoices; purchasing confirms which old PO items are finished; MR11 cleans approved residuals.
- Close: regrouping runs, and the controller reviews the aging of GR/IR by category.
- Monthly KPI: track the number and value of open items by age bucket. The goal is a stable or shrinking tail, not zero on day one.
Common mistakes to avoid
- Clearing by supplier only. Grouping only by supplier can match unrelated items and makes the audit trail harder to follow. Clear by purchase order and item.
- Using MR11 as a monthly plug. If MR11 volume grows every month, the problem is upstream: receiving discipline, invoice capture or service entry.
- Ignoring services. Service purchase orders without proper service entry sheets or confirmations are a major source of “invoiced but not received” items.
- No reversal of regrouping. Forgetting to reverse regrouping postings doubles the effect in the next period.
- Treating GR/IR as an AP-only account. It is a shared process account. Purchasing and logistics need to see it and own their part.
FAQ: GR/IR clearing in S/4HANA
Does S/4HANA clear the GR/IR account automatically?
Not by itself. You still need to configure clearing criteria and run or schedule automatic clearing (F.13 / SAPF124). What S/4HANA adds is better visibility and the Fiori monitor to manage exceptions.
Is F.19 still used in S/4HANA?
F.19 is tied to classic general ledger regrouping. In S/4HANA, GR/IR regrouping is typically performed with FAGLF101 and its configuration. Validate on your release before the first close.
What is the difference between F.13 and MR11?
F.13 clears items that already balance. MR11 posts the difference for items that will not balance on their own, such as small value differences or quantities that will never be invoiced, and closes them.
How often should we clean the GR/IR account?
Run automatic clearing at least weekly and before every close. Review aged exceptions monthly with purchasing and AP. A quarterly clean-up is usually too late.
Final thought
A clean GR/IR account is a sign of a healthy purchase-to-pay process. The tools in S/4HANA are mature; the difference between a clean account and a growing one is a scheduled job, a clear write-off policy, and named owners for exceptions.
Contact advisory if you want a practical review of your GR/IR process and close routine before the next year-end.