Goods Received Not Invoiced (GRNI)

Goods received not invoiced (GRNI) is the accrued liability for received goods with no matching vendor invoice yet. Here is what it is and why it ages.

Twitter LinkedIn WhatsApp
Ask AI: ChatGPT Claude Gemini Grok
Goods Received Not Invoiced (GRNI)

Goods received not invoiced is the accounting state where a receipt has been logged against a purchase order but no matching vendor invoice has arrived yet. It exists on the balance sheet as an accrued liability and in the AP queue as an open item waiting to close. The gap between receipt and invoice is where several distinct problems hide, from ordinary vendor billing delays to charges that never get billed correctly at all.

This page defines the term and explains what an aged GRNI balance tells an AP team, a controller, and an auditor, each looking for something different in the same list. Goods received not invoiced sits earlier in the AP lifecycle than most drift types: it is a pending state, not a completed error, and understanding that distinction is what separates normal timing from an exception worth investigating.

1. What is goods received not invoiced?

Goods received not invoiced (GRNI) is an accrued liability account that captures goods or services a company has received and recorded, for which no vendor invoice has yet been matched and posted in accounts payable. It is created automatically by three-way matching workflows: a purchase order is issued, a receipt is logged against it, and the system holds the expected cost as a liability until an invoice arrives to close it out.

The account exists because receiving and invoicing rarely happen on the same day. A delivery can post to inventory or expense on Monday while the vendor's invoice does not arrive until three weeks later. GRNI is the placeholder that keeps the books accurate in between.

Every ERP with purchase order workflows generates this account by default. It is not optional accounting; it is a structural byproduct of matching receipts to invoices.

2. Why does a GRNI balance grow?

A GRNI balance grows for two very different reasons: normal invoice timing, where a vendor simply bills weeks after delivery, and unresolved exceptions, where a receipt was logged against the wrong purchase order, quantity, or price, and no invoice can match it cleanly. The first resolves itself over the next billing cycle. The second sits and ages until someone investigates the mismatch line by line.

A receipt recorded at the wrong unit cost, or against a purchase order line that has since been changed, will never find a matching invoice automatically. It waits in GRNI indefinitely unless someone reconciles it by hand.

Vendors that consolidate billing monthly or quarterly also inflate the balance without anything being wrong. Distinguishing the two requires looking at individual line items, not the total.

3. How should an aged GRNI line be investigated?

An aged GRNI line is investigated by checking three things in order: whether the vendor actually issued an invoice for that receipt, whether the receipt itself matches what was ordered on the purchase order, and whether an invoice exists elsewhere in AP under a different reference number and was never matched. Each answer points to a different owner and a different fix.

If no invoice was ever issued, the vendor delivered goods it has not billed for, which is worth a direct call rather than a write-off.

If the receipt was logged incorrectly, purchasing or the receiving dock needs to correct the record before matching can succeed.

If a matching invoice already exists elsewhere, it is a routing failure inside AP, not a vendor issue at all.

4. How is GRNI different from a duplicate payment or a missed credit memo?

GRNI describes a liability waiting to be matched, before any payment has occurred. A duplicate payment and a missed credit memo both describe money that has already left the company, either paid twice for the same charge or never credited back after a return or overcharge. GRNI sits earlier in the AP lifecycle: it is a pending state, not a completed error.

That distinction matters for where a company looks for recovery. An aged GRNI item that never gets matched can eventually become a write-off, which is a control gap rather than cash already lost.

A duplicate payment or missed credit memo, by contrast, is money to recover now. Both problems can originate from the same weak matching process.

For the wider pattern this sits inside, start with the margin drift guide.

5. Frequently Asked Questions (People Also Ask)

What does GRNI stand for?

GRNI stands for goods received not invoiced. It is the accrued liability account that holds the value of goods or services a company has received and recorded, pending a matching vendor invoice.

Is a GRNI balance always a problem?

No. A current GRNI balance reflecting normal invoice timing, where a vendor bills days or weeks after delivery, is expected in any purchase order driven AP process. It becomes a concern only when specific line items age well past a vendor's typical billing cycle.

What causes a GRNI item to age instead of clearing?

A mismatch between the receipt and the eventual invoice, in quantity, unit price, or purchase order line, prevents automatic matching. The item then waits until someone manually reconciles the receipt, the purchase order, and the invoice.

Can an aged GRNI balance turn into cash recovery?

Sometimes. If investigation shows a vendor delivered goods or services it never billed for, that is a legitimate charge the company can pursue or negotiate, not automatically money owed back. If the receipt itself was recorded in error, correcting it is a controls fix rather than a recovery.

Who is responsible for clearing GRNI exceptions?

Responsibility typically splits across purchasing, receiving, and accounts payable, since each can be the source of the mismatch. A controller usually owns the aging review that flags which items need investigation.

How does GRNI relate to three-way matching?

GRNI is a direct output of three-way matching. The system compares the purchase order, the receipt, and the invoice, and any receipt without a matched invoice sits in GRNI until the third document arrives and reconciles.

Does GRNI appear on the balance sheet?

Yes. GRNI is recorded as an accrued liability, representing an obligation the company has incurred for goods or services received but not yet formally invoiced and paid.

What is the difference between GRNI and an accrued expense?

GRNI is a specific type of accrued expense tied to a purchase order and a physical or logged receipt. Accrued expenses more broadly can include costs with no purchase order at all, such as an estimated utility charge before the bill arrives.

1. What is goods received not invoiced?

Goods received not invoiced (GRNI) is an accrued liability account that captures goods or services a company has received and recorded, for which no vendor invoice has yet been matched and posted in accounts payable. It is created automatically by three-way matching workflows: a purchase order is issued, a receipt is logged against it, and the system holds the expected cost as a liability until an invoice arrives to close it out. The account exists because receiving and invoicing rarely happen on the same day. A delivery can post to inventory or expense on Monday while the vendor's invoice does not arrive until three weeks later. GRNI is the placeholder that keeps the books accurate in between. Every ERP with purchase order workflows generates this account by default. It is not optional accounting; it is a structural byproduct of matching receipts to invoices.

2. Why does a GRNI balance grow?

A GRNI balance grows for two very different reasons: normal invoice timing, where a vendor simply bills weeks after delivery, and unresolved exceptions, where a receipt was logged against the wrong purchase order, quantity, or price, and no invoice can match it cleanly. The first resolves itself over the next billing cycle. The second sits and ages until someone investigates the mismatch line by line. A receipt recorded at the [wrong unit cost](/glossary/rate-card), or against a purchase order line that has since been changed, will never find a matching invoice automatically. It waits in GRNI indefinitely unless someone reconciles it by hand. Vendors that consolidate billing monthly or quarterly also inflate the balance without anything being wrong. Distinguishing the two requires looking at individual line items, not the total.

3. How should an aged GRNI line be investigated?

An aged GRNI line is investigated by checking three things in order: whether the vendor actually issued an invoice for that receipt, whether the receipt itself matches what was ordered on the purchase order, and whether an invoice exists elsewhere in AP under a different reference number and was never matched. Each answer points to a different owner and a different fix. If no invoice was ever issued, the vendor delivered goods it has not billed for, which is worth a direct call rather than a write-off. If the receipt was logged incorrectly, purchasing or the receiving dock needs to correct the record before matching can succeed. If a matching invoice already exists elsewhere, it is a routing failure inside AP, not a vendor issue at all.

4. How is GRNI different from a duplicate payment or a missed credit memo?

GRNI describes a liability waiting to be matched, before any payment has occurred. A duplicate payment and a missed credit memo both describe money that has already left the company, either paid twice for the same charge or never credited back after a return or overcharge. GRNI sits earlier in the AP lifecycle: it is a pending state, not a completed error. That distinction matters for where a company looks for recovery. An aged GRNI item that never gets matched can eventually become a write-off, which is a control gap rather than cash already lost. [A duplicate payment](/glossary/duplicate-payment) or missed credit memo, by contrast, is money to recover now. Both problems can originate from the same weak matching process. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide.

Questions & Answers

What does GRNI stand for?

GRNI stands for goods received not invoiced. It is the accrued liability account that holds the value of goods or services a company has received and recorded, pending a matching vendor invoice.

Is a GRNI balance always a problem?

No. A current GRNI balance reflecting normal invoice timing, where a vendor bills days or weeks after delivery, is expected in any purchase order driven AP process. It becomes a concern only when specific line items age well past a vendor's typical billing cycle.

What causes a GRNI item to age instead of clearing?

A mismatch between the receipt and the eventual invoice, in quantity, unit price, or purchase order line, prevents automatic matching. The item then waits until someone manually reconciles the receipt, the purchase order, and the invoice.

Can an aged GRNI balance turn into cash recovery?

Sometimes. If investigation shows a vendor delivered goods or services it never billed for, that is a legitimate charge the company can pursue or negotiate, not automatically money owed back. If the receipt itself was recorded in error, correcting it is a controls fix rather than a recovery.

Who is responsible for clearing GRNI exceptions?

Responsibility typically splits across purchasing, receiving, and accounts payable, since each can be the source of the mismatch. A controller usually owns the aging review that flags which items need investigation.

Margin Drift Resources