Uncleared receipts and invoices, with reasons attached
SAP ships apps for this one, so this page makes a narrower claim. Month end is still slow, because monitoring uncleared items is not the same as knowing why each one is stuck, and today the why is worked out by a person, line by line.
◆ The ritual, honestly statedthe apps exist, and the work remains.
Goods receipts and invoice receipts post to a clearing account and are matched against each other per purchase order line. Standard monitoring apps exist and show the uncleared items, so no claim here that the report is missing. The claim is narrower and holds: the month end around those apps is a ritual. A regrouping run reclassifies the balance for the financial statements. Automatic clearing sweeps the easy matches and leaves the rest.
What remains is the expensive part. Every aged uncleared item is stuck for a reason, and the standard views show the item without the reason. Someone opens the purchase order history line by line, decides whether it is a quantity gap, a price gap, a missing invoice, or a missing receipt, and routes it. That decision loop, repeated across hundreds of items, is where the closing days go.
◆ Root causes by rulefour patterns cover most of the list.
| Root cause | How a rule detects it | Who gets it |
|---|---|---|
| Quantity mismatch | Received quantity and invoiced quantity disagree on the line. | Warehouse or vendor, depending on sign. |
| Price mismatch | Quantities agree, values differ. Often a PPV story too. | Purchasing, against the order price. |
| Missing invoice | Receipt posted, no invoice after a set number of days. | Accounts payable, to chase the vendor. |
| Missing receipt | Invoice posted, no receipt behind it. | Receiving, or a fraud check if it persists. |
None of these rules is clever. Their value is that they run before the person looks, on every open line, 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 month-end worklist, oldest and largest first
SELECT po_line, root_cause, days_uncleared, open_value
FROM fct_grir_open_line
WHERE snapshot_date = DATE '2026-07-31'
ORDER BY open_value DESC, days_uncleared DESC
- 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.
- PPV
- Purchase price variance, the gap between price paid and standard cost.