Goods received not invoiced (GRNI) describes accepted receipts for which the corresponding supplier invoice has not posted or matched at the reporting cutoff. Reconcile the balance at the receipt line. Start with accepted receipts, subtract posted returns and the quantities on invoices matched to those receipts, then investigate what remains. A purchase order can have several shipments and partial invoices, so its header status hides which delivery is still open.
Oracle documents a period-based uninvoiced receipt report for reviewing amounts due for accrual or already accrued. Your system and policy determine which receipts affect accounting. The workflow below builds a reproducible review of the underlying receiving and invoicing records.
Agree which records belong at the cutoff
Take dated extracts of posted receipts, returns, and invoice match links. Keep legal entity, purchase order line, receipt transaction and line, supplier, currency, unit of measure, and relevant posting dates. Ask finance which cutoff and period it owns and which system fields represent posting. Keep arrival, acceptance, invoice entry, and invoice posting distinct; a truck arriving at the dock does not establish that the receipt was accepted and posted.
Keep unmatched invoices and receipt rows with missing match keys on an exception list. A supplier total can tie by coincidence when two unrelated lines offset. For example, Dynamics 365 matches invoice quantities to selected product receipts in three-way matching. In your export, keep the specific receipt link where the ERP provides it and assign unmatched rows to an owner when it does not. See three-way matching for the invoice approval workflow itself.
Build the open balance from posted quantities
In this synthetic example, one order has two receipts at an agreed $12 per unit. All counted units are in the same unit of measure and currency. The cutoff is November 30. The supplier issued one posted invoice matched to the first receipt, and the receiving team posted a return against the second receipt.
| Receipt and date | Accepted | Return posted | Invoice matched | Unmatched at cutoff |
|---|---|---|---|---|
| R101, November 14 | 80 | 0 | 60 | 20 units ($240) |
| R102, November 26 | 40 | 5 | 0 | 35 units ($420) |
The operational report shows 55 unmatched units and an estimated $660 at the order price. The two open quantities have aged 16 days and four days using calendar days from receipt. If a second invoice for 20 units posts and matches R101 on December 2, it clears that line in the next dated view. Preserve the November snapshot and add the December posting as follow-up evidence. The estimate excludes taxes, freight, exchange rates, and any accounting adjustments. Use the ERP’s posted values to reconcile financial balances.
Aggregate matched invoice quantities to receipt line before joining the receipts. A single invoice can cover multiple receipts and a receipt can have multiple invoices. Use the matched amounts for the relevant line, keep conversions explicit, and preserve documented returns and credit relationships. Flag negative unmatched quantities for investigation instead of clipping them to zero. A return after an invoice, a credit, or a double match can each produce a different follow-up.
Assign the exception to the team that can resolve it
Receiving checks disputed quantities and missing return references. Accounts payable confirms whether the invoice arrived and was matched to the right delivery. Purchasing resolves price and unit discrepancies with the supplier. The controller owns period policy and approval of any financial adjustment. Record the source ID, decision, and next owner each time an exception changes hands so the close team can distinguish an expected lag from a missing record.
Where Permute fits in the receipt review
Permute sells connected business data, custom applications, and governed analysis. We can combine permitted receiving, return, and invoice extracts using your receipt-line keys and cutoff rules. A reviewer can see which matched entries account for a balance, explore the unmatched quantity within their permissions, and send the source reference to the team that owns the correction.
Bring the receipt references together
Load permitted receipt and invoice extracts with their matching keys.
Keep accounting and source corrections with their owners
We read from connected systems for this review. The finance team decides how to account for balances and what to post. Retain an unknown balance when source extracts are incomplete or mismatched. Validate receipt totals and unmatched invoice counts against the source before relying on the report. The procure-to-pay process describes where the records originate and who owns their handoff.
Start the GRNI review with accepted receipts and the invoice quantities tied to them at the cutoff. Keep returns and unmatched invoices visible so a coincidental order total cannot hide a missing link. Assign each old balance to the team that can verify its next event.
Trace one old open receipt
Bring permitted receiving and invoice references to compare what the teams can match at the same cutoff.
Questions about open purchase receipts
What if the invoice arrived before it posted?
Keep the invoice arrival or entry date as a separate diagnostic. Use the posting and match rules agreed for the report cutoff and let finance determine the treatment for that period.
Does an unreceived purchase order belong in GRNI?
An open order is a purchasing record. Include the quantity only when an accepted receipt qualifies under the report scope. Keep the quantity still due on the order in a separate column or report.