Analytics Catalog/SAP S/4HANA/GR/IR aging
Explore the catalogModulesPurchase price varianceAccounts payableOpen items as of a past dateExtraction pattern
SAP S/4HANA · Purchasing · Editorial

Uncleared receipts and invoices, with reasons attached

SAP's Reconcile GR/IR Accounts app already shows why a line is stuck, such as a missing receipt or a quantity gap. Recording the root cause is still a person's job unless you license its machine learning or code a rule, and the app reads only current data.

RuleAge uncleared GR/IR at the purchase order line, assign a root-cause category by rule, and start month end from the worked list.
Nevertreat the clearing account balance as the workload. The balance nets opposite-signed problems that each need their own fix.
Uncleared items receipts versus invoices Reasons attached root cause per line The worklist oldest and largest first
A category written by rule on every line, before anyone opens one, is what takes days out of month end.
◆ What the app does, and what it leavesthe situation is shown, the decision is still typed.

Goods receipts and invoice receipts post to a clearing account and are matched per purchase order line. The Reconcile GR/IR Accounts app (F3302) builds a worklist of lines whose receipts and invoices differ, shows a smart fact such as no goods receipt yet or a quantity difference, and lets a processor record status, priority, and root cause. A regrouping run reclassifies the balance; automatic clearing sweeps the easy matches.

What remains is the recording. Root cause and processor are set by hand unless you buy the machine learning add-on, which needs a separate license and learns from past manual choices, or code a BAdI rule that a scheduled job applies (status October 2026). The app also reads only current data, so lines moved to the historical area by data aging drop out.

◆ Root causes by rulefour patterns cover most of the list.
Root causeHow a rule detects itWho gets it
Quantity mismatchReceived quantity and invoiced quantity disagree on the line.Warehouse or vendor, depending on sign.
Price mismatchQuantities agree, values differ. Often a PPV story too.Purchasing, against the order price.
Missing invoiceReceipt posted, no invoice after a set number of days.Accounts payable, to chase the vendor.
Missing receiptInvoice posted, no receipt behind it.Receiving, or a fraud check if it persists.

The app's smart facts flag the same four situations. The difference is that these rules write the category on every open line before anyone looks, and the warehouse keeps it, so the human minutes go to the residual cases the rules cannot classify.

◆ The owned answeraging by line, category by rule, list by owner.

The build is an aging fact at the purchase order line grain in your warehouse: days uncleared, open quantity and value on each side, and the rule-assigned root-cause category.

Month end starts from that worked list, sorted by age and value, split by owner. The same landed tables feed the PPV cube, and the aging itself follows the snapshot discipline of open items as of a past date, so last month’s list is still there next quarter.

The worklist above is a sort over the open-line snapshot: oldest and largest first, root cause attached. The open-line snapshot is drawn on the SAP owned-model reference; the table above is what it delivers.

Use case
Problem
The GR/IR app shows each line's situation, but the root cause is typed by hand unless you license its machine learning or code a rule, so month end still goes one purchase order line at a time.
What we build
A purchase-order-line aging of uncleared GR/IR in your warehouse, with root-cause categories assigned by rule and a daily snapshot kept.
What you get
A month end that starts from a worked list split by owner, with human time spent only on the residual the rules cannot classify.
How many closing days go to stuck receipts?
We ship the rule-categorized worklist so the investigation starts finished.
Talk to us
Terms on this page
SAP
The vendor. Systems, Applications, and Products in data processing.
HANA
SAP’s in-memory database, the platform S/4 runs on.
ERP
Enterprise resource planning, the system of record for operations and finance.
GR
Goods receipt, the posting that records arrival of purchased material.
IR
Invoice receipt, the posting that records the vendor’s invoice.
clearing account
The account where receipts and invoices wait to be matched.
regrouping
The month-end run that reclassifies the clearing balance for the statements.
smart fact
The app's label for a line's situation, such as no invoice yet or a quantity difference.
BAdI
Business Add-In, SAP's hook for custom code in a standard process; here FINS_GRIR_STATUS_RULE.
data aging
Moving old documents to a historical area that the app does not read.
PPV
Purchase price variance, the gap between price paid and standard cost.