Goods Received Not Invoiced: GRNI Workflow Guide

Goods received not invoiced means your business has already taken delivery of goods, but Accounts Payable cannot yet match and post the supplier invoice. In plain terms, the cost has arrived operationally before it has cleared financially. That is why goods received not invoiced sits as an open liability balance in GRNI or GR/IR clearing: under accrual accounting, you owe for what you have received even if the invoice is late, incomplete, or not yet matchable. At month-end close, some of that balance is normal. Some of it is not.

A healthy procure-to-pay process can still show open GRNI near cutoff because timing differences are real. A truck unloads on March 31, but the invoice lands on April 2. A supplier sends one consolidated bill for multiple deliveries. A warehouse records a partial receipt before the final quantity is confirmed. Those are routine cases. Persistent balances usually point to late invoices, partial receipts that were never updated, missing purchase order references, quantity differences, price mismatches, or invoice documents that are hard to match to the underlying receipt.

The operational meaning matters just as much as the accounting meaning. Your team may not have an invoice approved for payment yet, but the business has still taken possession of stock, raw materials, or supplies. That creates a real obligation, which is why GRNI reconciliation is not just a cleanup exercise for AP. It is a control point between purchasing, receiving, and invoice processing. The fastest way to clear an item is usually to trace the purchase order, the receipt evidence, and the invoice together and ask one practical question: is this an expected timing difference, or is there a document or matching problem blocking clearance?

A practical GRNI investigation workflow looks like this:

1. Review the open report and isolate the item.
2. Build the evidence pack: PO, receipt evidence, delivery note, invoice, and accrual support.
3. Identify whether the issue is timing, receipt status, quantity, price, or invoice-structure mismatch.
4. Route the item to the team that owns the next fact.
5. Classify the outcome as accrue, clear, escalate, or write off.

You may also see this described as received not billed. In most finance teams, received not billed vs received not invoiced is mostly a wording difference rather than a process difference. Both refer to goods or services received before billing has been fully matched and cleared. For the rest of this guide, the useful lens is simple: treat fresh, explainable items as timing, and treat aging or unclear items as exceptions that need investigation.

Start With the Report and the Full Evidence Pack

Before you try to clear anything, read the received but not invoiced report as an investigation queue, not just an account listing. Sort it so you can see aging, receipt date, supplier, purchase order, and line-level or open-item detail together. That view tells you which items are fresh month-end timing differences and which ones are old enough to need evidence tracing. It also stops you from treating every open balance as the same problem.

For each line you review, capture the facts that matter first: when the goods were received, how long the item has been sitting open, which supplier is involved, which PO or receipt reference is attached, and whether the balance sits at summary level or broken out by receipt or line. A proper goods received not invoiced reconciliation starts with this report hygiene. If the report only shows a net supplier balance with no receipt or PO detail, pull the supporting transaction history before you go any further.

Then build one evidence pack per open item. In most environments that pack should include:

• The purchase order
• The goods received note (GRN) or other goods receipt evidence
• The delivery note or packing slip
• The supplier invoice, if one exists
• Any accrual support or month-end close documentation already attached to the balance

Treat a missing document as a clue. If there is no invoice, that may support a true timing difference. If there is no GRN or other receipt evidence, the issue may be with receipt posting rather than invoicing. If the delivery note exists but the receipt record does not, you already know where the document chain breaks.

Once the pack is assembled, compare the documents line by line. Check dates, quantities, unit prices, vendor identifiers, PO numbers, receipt references, and line-item splits. Confirm that the invoice and receipt actually relate to the same commercial event, not just the same supplier. A common trap is assuming that any invoice with a familiar vendor name belongs to the receipt on the report, when the shipment, billing period, or PO coverage is different.

Be especially careful with split lines and rolled-up billing. One receipt may cover several SKU lines, while one invoice line may summarize multiple deliveries. The job here is not to force a match too early. The job is to establish whether the PO, the receipt evidence, the delivery note, and the invoice describe the same goods, in the same quantities, at the same agreed price basis.

If you repeat this structure for every open line, later review becomes much faster. Everyone works from the same facts, the same document set, and the same item-level history instead of re-creating the file from scratch each time.

The Main Reasons GRNI Balances Do Not Clear

Not every open GRNI item is a problem. Sometimes it is simply a late supplier invoice at month end: the goods were received before close, the PO is valid, and the invoice has not arrived or has not been entered yet. In that case, the receipt record is usually the temporary source of truth, and your next action is to confirm expected invoice timing, not to treat the balance as a breakdown.

The harder cases are true goods receipt invoice mismatch situations. Most persistent items fall into a few repeatable patterns:

• Partial receipt: the supplier bills for the full order, but your warehouse has posted only part of the delivery or spread receipts across multiple dates. Start with the PO line history and the individual receipt records.
• Consolidated invoice: one invoice spans several POs, several receipt events, or both. Split the bill into its commercial components before deciding whether anything is wrong. This is the same issue covered in how to handle one supplier invoice across multiple purchase orders.
• Quantity difference: the invoice quantity does not match what was physically received. Start with the goods receipt, delivery note, return record, or damaged-goods note.
• Price difference: the quantities align but the billed value does not. Move to the PO, contract, approved supplier price list, and any freight or surcharge support.

Another common gap is receipt-to-invoice visibility. If the invoice does not clearly reference the receipt event it belongs to, and your team cannot see how long that receipt has been waiting for a bill, normal timing items and broken exceptions start to look the same.

A large share of three-way matching exceptions starts upstream, before anyone tries to clear GRNI. Missing PO references, wrong PO numbers, inconsistent vendor names, buried receipt references, and invoice layouts that hide key fields in footers, side panels, or free-text notes make legitimate invoices look unmatched. In those cases, the invoice is not a reliable matching document until its data is clarified, so the immediate job is to rebuild the link between invoice, PO, and receipt using supplier identity, invoice number, dates, descriptions, and supporting documents.

That is why good invoice exception management is not only about downstream clearing mechanics. It is also about whether invoice data arrives in a usable structure. If your team uses Invoice Data Extraction, structured extraction can pull invoice numbers, vendor names, PO references, quantities, pricing, and totals into consistent Excel, CSV, or JSON output, with the source file and page reference attached to each row. That helps AP rebuild the link between an invoice and a specific receipt event instead of spending the close re-entering ambiguous supplier documents by hand.

---

Who Should Own Each Step of a GRNI Investigation

A workable GRNI reconciliation process starts with one rule: the item stays with the team that can prove the next fact, not the team that discovered the problem. That keeps open balances from bouncing around during month-end close. Each exception should have a named document owner, a clearly stated reason for the handoff, and an expected next action tied to the evidence already collected.

• AP owns the invoice side. AP confirms whether the supplier invoice has been received, whether the key fields were captured correctly, and whether matching failed because of missing references, price differences, quantity differences, or a missing invoice altogether. If AP cannot link the invoice to the purchase order and receipt evidence, the handoff should say exactly why.
• Receiving owns the receipt side. Receiving confirms what physically arrived, whether the receipt was posted correctly, whether the quantity was partial or complete, and whether the delivery note or goods receipt support matches what the system shows.
• Procurement or vendor management owns supplier and PO resolution. If the invoice is late, the purchase order is wrong, pricing changed, or the supplier billed in a way that does not line up with the receipt pattern, this team chases the vendor and fixes the commercial or document issue.
• Controllership owns policy and aging discipline. Controllership sets cutoff rules, aging buckets, materiality thresholds, and the policy for when an item stays as a valid accrued balance versus when it must be escalated for cleanup.

Hand off each item with the evidence pack, not with opinion. A useful handoff note has four fields: document reviewed, exception identified, owner, and due date. For example: "Receipt posted for 80 units on March 28, invoice not received as of close, supplier confirmed billing next week, procurement follow-up due April 3."

Simple aging triggers also help. For example, keep fresh items with AP for initial review, move items with unresolved receipt questions to receiving within a few business days, escalate supplier or purchase order issues to procurement if they remain open past the first review cycle, and require controllership review for older balances, such as anything still open after 30 days or crossing a set materiality threshold. The exact timing can vary, but the principle should not: no GRNI item should sit in a queue without a named owner, next action, and review date.

Decide Whether to Accrue, Clear, Escalate, or Write Off

At period end, every open item should end in one of four buckets. The goal during month-end close is not to force GR/IR clearing for appearance's sake. It is to separate a real liability from a preventable matching exception and document the right next action.

According to APQC-backed accounts payable benchmark data on invoice-error resolution, top-performing companies clear invoice errors in three days, median performers need five days, and lowest-performing companies need at least seven days. That matters because slow exception handling turns a manageable close issue into a recurring GRNI backlog.

1. Accrue when the goods were received before cutoff, the receipt evidence is valid, and the supplier liability is real even though the invoice has not arrived or is still in transit. In accrual accounting, this is a valid GRNI accrual: you have the economic obligation, but not yet the final invoice. Keep supporting evidence with the PO, receipt, expected value, and cutoff date so the balance is explainable.

2. Clear when the invoice has arrived and the documents now align. If the PO, receipt, quantities, and pricing match, stop treating the item as an investigation case and move it through normal posting and clearing. This is the cleanest form of GR/IR clearing because the timing gap has closed and the balance no longer represents an open exception.

3. Escalate when the evidence shows a real mismatch or a missing action. Price differences go to procurement or vendor management. Quantity differences and receipt-status issues go to receiving or warehouse operations. Missing invoices or incomplete supplier documents stay with AP follow-up, and this is where disciplined accounts payable cutoff procedures for late invoices help you distinguish a true timing issue from a control failure.

4. Write off or apply policy-based cleanup only when the residual is old, low value, unsupported, or clearly caused by historic posting noise that will not reverse through normal processing. This is not a shortcut for unresolved exceptions. The exact accounting treatment depends on your company policy, materiality thresholds, and audit requirements, so the item should be documented, approved, and coded according to your close policy.

A disciplined close owner uses these four outcomes to classify, not just eliminate, open balances. Valid accruals stay supported, matched items clear, real exceptions escalate to the right owner, and aged residuals move to controlled cleanup only when policy allows.

---

Reduce Recurring GRNI Cleanup by Fixing Invoice Data Upstream

If the same goods received not invoiced balances keep reappearing, the problem usually starts before month-end reconciliation. Supplier invoices arrive with missing purchase order references, vague line descriptions, price mismatches, partial-billing patterns, or multiple POs rolled into one document. That forces AP to interpret the invoice before three-way matching can even begin, which is why goods received not invoiced reconciliation often turns into detective work instead of a controlled review.

The fix is not only a better close checklist. It is cleaner invoice evidence from the start. When invoice data is captured consistently, AP can compare supplier billing against receipts and PO data with less rekeying, fewer judgment calls, and a smaller pile of exceptions that sit in GRNI waiting for someone to decode them. In practice, the fields that matter most are:

• Invoice number
• Vendor name
• PO reference
• Quantities
• Unit prices and line values
• Invoice totals
• A clear link back to the source document used in the review

This is where invoice extraction software for cleaner three-way matching can materially reduce manual effort without changing the control framework. For example, if one supplier invoice covers several receipts and hides the PO reference in a footer, Invoice Data Extraction can pull the PO number, quantities, pricing, totals, and source file or page references into structured Excel, CSV, or JSON outputs. AP gets a cleaner evidence pack for exception triage, especially when invoices have inconsistent layouts, multiple pages, or line-item detail that is tedious to re-enter by hand. The boundary matters: extraction improves the quality and traceability of the data used in review, but it does not post to your ERP, clear GRNI automatically, or make disposition decisions on your behalf.

Some businesses reduce invoice friction through receipt settlement, where the receipt drives settlement without a traditional supplier invoice in every case. That can reduce certain matching exceptions, but it does not eliminate the need for standard GRNI investigation wherever supplier invoices, receipt records, and PO terms still need to be checked together. If you operate in a more complex environment, the same prevention logic applies, and these manufacturing-specific GRNI reconciliation steps show how that review often plays out when partial receipts and pricing variances are common.

To turn this article into a working prevention plan, build your investigation checklist around the recurring upstream failure points. Track which GRNI items were caused by missing PO numbers, pricing discrepancies, partial receipts, invoice layout issues, or multi-PO billing. Then tighten your invoice capture rules so those fields are extracted in a consistent structure before review starts. That is how you move from one-off cleanup to a repeatable goods received not invoiced reconciliation process that gets faster each close.