Goods Received Not Invoiced (GRNI): Meaning and Accounting
Jul 9, 2026
Jul 9, 2026
Convert a purchase order to Excel, CSV, or JSON
Submit your purchase orders
Drop documents here, or click to file
Up to 50 files per batch
Uploading...
Goods received not invoiced (GRNI) is the value of items your business has received but has not yet been invoiced for by the supplier. The goods are in your possession and the liability is real, but accounts payable cannot post the invoice yet because it has not arrived or has not been matched. GRNI is recorded as an accrued liability so your books show what you owe, even before the paperwork catches up.
Last updated July 2026.
GRNI reconciliation depends on tying receipts back to the right purchase order. If your POs arrive as PDFs, you can upload one above and get the PO number, supplier, and line items back as structured data in seconds, so finance can match receipts to orders instead of chasing paper.
Goods received not invoiced, often shortened to GRNI or GRN, means a delivery has arrived and been recorded, but the matching supplier invoice has not yet been posted to accounts payable. It represents a genuine obligation: you have the goods, so you owe for them, even though the final invoice is still in transit or held in a matching exception. In accrual accounting, that obligation has to appear on the balance sheet in the period the goods were received.
The GR/IR clearing account, short for goods receipt / invoice receipt, is a temporary holding account in the general ledger that bridges the gap between receiving goods and posting the invoice. When goods arrive, the system debits inventory or expense and credits GR/IR. When the invoice is posted and matched, the entry reverses: GR/IR is debited and accounts payable is credited. If the invoice value equals the received value, the GR/IR account nets to zero for that transaction. It is also called the purchases clearing or goods-in-transit account.
GRNI is handled as an accrual so the expense and liability land in the correct period. The two-step treatment looks like this:
When the received value and the invoiced value agree, the clearing account balances to zero. A residual balance signals a mismatch to investigate: a price difference, a partial delivery, or an invoice that never came.
Yes. Goods received not invoiced is a valid accrual when the goods were received before the period cutoff, the receipt evidence is sound, and the supplier liability is real even though the invoice has not arrived. You credit the GRNI or GR/IR account instead of accounts payable, because there is no invoice to post yet, and debit inventory or expense. The accrual makes sure the cost is recognized in the period the goods were used, not the later period the invoice happens to arrive.
An unmanaged GRNI balance quietly distorts the accounts. Left alone, it understates liabilities if receipts are missed, or overstates them if old accruals are never cleared. At month-end and year-end, controllers reconcile the GR/IR account line by line to separate two very different things: real liabilities where the invoice is simply late, and stale exceptions that should be cleared because the invoice will never come, was already posted, or the receipt was wrong. The goal is not to force the balance to zero for appearance, but to explain every open item.
Most GR/IR reconciliation problems come from a handful of recurring issues:
Nearly all of these trace back to how cleanly receipts and orders are captured. When the goods receipt note and the purchase order carry accurate, matching line-item data, the GR/IR account clears itself far more often.
The GR/IR account clears when the invoice matches the receipt and the receipt matches the order. That chain breaks when the underlying data is keyed by hand or captured incompletely. Extracting purchase orders into structured fields, PO number, supplier, quantities, unit prices, and line totals, gives finance a reliable benchmark to match receipts and invoices against. Teams that also remove manual work on the invoice side by moving to automated accounts payable processing shrink the pool of unmatched items that turn into GRNI in the first place.
Scope note: extraction produces match-ready data. It does not post journal entries or clear the GR/IR account, which stays in your ERP or accounting system where the controls and audit trail belong.
Accounts payable holds liabilities where a supplier invoice has been received and posted. GRNI holds liabilities where goods have been received but no invoice has posted yet. GRNI is an accrual in a clearing account; once the invoice arrives and matches, the balance moves out of GRNI and into accounts payable as a formal payable.
You reconcile GR/IR by reviewing each open item and identifying why it has not cleared. Match receipts to invoices, then resolve the exceptions: chase missing invoices, correct price or quantity mismatches, and reverse receipts posted in error. Real late invoices stay accrued; items that will never invoice are cleared with the proper adjustment and documented for audit.
Yes. Goods received not invoiced is reported as a current liability, usually as an accrued liability or within accruals, because it represents an obligation the business expects to settle within the normal operating cycle once the supplier invoice is received and matched.
A GRNI balance grows when receipts pile up without matching invoices. The usual drivers are suppliers that bill late or not at all, invoices stuck in matching because of price or quantity differences, and goods receipts posted against the wrong purchase order. Poor purchase order and receipt data makes all three more frequent, which is why clean capture reduces the balance.