What is GR/IR (goods-received-not-invoiced), and how do I reconcile and control it?

GRNI balloons from four habits: receipts entered for goods whose invoices post unmatched (so nothing clears), price/quantity variances that leave residuals on cleared lines, canceled or changed POs whose receipts were never reversed, and invoices posted before receipts (IR-before-GR). The fix is matching discipline - invoices must match against their receipts, not post alongside them - plus a monthly aging of open GR/IR items by PO line.

Age the open items by PO line, then triage: items under 90 days are normal pipeline; 90 days to a year get vendor/PO investigation (will an invoice ever come?); older than a year are write-off candidates after confirming the PO is dead. Write off with documentation (reverse the accrual to the original expense/inventory account), then install the monthly aging so the backlog never rebuilds.

In SAP, goods receipt (MIGO) debits inventory/expense and credits GR/IR; invoice receipt (MIRO) debits GR/IR and credits the vendor. Matched lines net to zero; the open balance is receipts awaiting invoices (or invoices awaiting receipts) by PO line item.

Pull open GR/IR items by PO line, match receipts to invoices by line and quantity, classify open items (awaiting invoice, awaiting receipt, variance residual, dead PO), validate large/old items against vendor and buyer records, and document the closing balance composition. The reconciliation is a list of explained open items, not a single number.

After confirming the PO is closed and the vendor won't bill (typically 12+ months old), reverse the GRNI: debit GR/IR, credit the original expense or inventory account - with approval and documentation, since you're releasing a recorded liability to income.

MR11 (account maintenance) clears residual open quantities/values on PO lines that will never match - actually closing the items. F.19 reclassifies the open balance for financial statement presentation at period-end without clearing anything. Use MR11 to clean, F.19 to present; teams that only run F.19 are formatting the problem, not fixing it.

IR-before-GR flips the account: it carries a debit (asset-like) balance representing invoices for goods not yet received - either a receiving-entry lag or goods genuinely not delivered. Both deserve investigation; chronic IR-before-GR means receiving discipline is broken or the matching policy lets invoices bypass receipts.

The mechanics are equivalent even when the account name differs: item receipts or receiving transactions accrue the liability into an accrued-purchases/received-not-billed account, and vendor bill matching clears it. NetSuite uses item receipts against accrued purchases; Intacct and Acumatica clear through PO receipt workflows; D365 posts product receipts that invoice posting reverses. The reconciliation discipline is the same everywhere.

A net credit GRNI balance is a current liability (goods received, payment obligation exists). Debit components (IR-before-GR) should be reclassified for presentation rather than netted invisibly - that's exactly what SAP's F.19 regrouping does at period-end.

Make receiving the gate for payment (no receipt, invoice stalls - which the field hears about), give receivers a mobile/portal flow at the dock or site, and report unreceived-PO aging to operations leadership weekly. In industries with field delivery (construction, healthcare), moving receipt confirmation to the requester is the unlock.

Joint ownership with one accountable name: AP runs the reconciliation (they see the invoice side), procurement resolves dead POs and variance disputes, inventory accounting signs off on balance-sheet presentation. The failure mode is everyone assuming it's someone else's account.

Each receipt and each invoice posts at line level, so a PO line can carry multiple receipts matched by multiple invoices - clearing happens progressively, and timing mismatches leave temporary open slices. Many-to-many matching is normal; it only becomes a problem when residual slivers are never reviewed.

A healthy GRNI typically represents roughly two to six weeks of PO spend - the natural receipt-to-invoice lag. Worry when the balance exceeds a month or two of spend, grows faster than purchase volume, or contains items older than 90 days that nobody can explain.

An item-level listing of the closing balance by PO line with age, an explanation category for each material item, evidence of investigation for old items, write-off documentation with approvals, and a preparer/reviewer sign-off. "The system calculates it" is not a reconciliation - the workpaper proves a human understood the composition.

Receipts post at PO price; invoices post at invoice price. Price differences hit variance accounts (or inventory revaluation) while quantity differences leave open slices on the line. Tolerance settings decide which variances auto-clear and which block - too-loose tolerances hide cost leakage, too-tight ones bury AP in exceptions.

Stampli's PO matching links invoices to POs and receipt data at the line level - Stampli AI performs line-level matching even with inconsistencies - so invoices clear against their receipts instead of posting around them, which is the behavior that keeps GRNI from accumulating. Receiving captured in Stampli Procurement gives AP the received-not-invoiced view that doubles as the accrual basis and the reconciliation starting point.