GRNI Reconciliation: How to Clear Goods Received Not Invoiced Without Month-End Guesswork
The Account Nobody Owns
Every month-end, somewhere between the warehouse and the general ledger, a number gets decided. It is the value of goods the business has received but not yet been invoiced for, and it goes by GRNI, goods received not invoiced, or in SAP environments, GR/IR clearing.
In theory this is the most defensible accrual on the balance sheet. It is not an estimate. It is built from actual goods receipt transactions with dates, quantities and purchase order prices attached. Compared to a manual accrual for professional services, where finance is genuinely guessing, GRNI should be the easy one.
In practice it is often the least trusted number in the close. The balance grows quarter over quarter, nobody can explain the aged portion, procurement says the goods were never received, AP says the invoice was already paid, and the controller ends up making a judgement call on a balance that is supposed to be evidence-based.
The reason is ownership. GRNI sits at the intersection of three functions and is owned by none of them. Procurement raises the order and stops paying attention once goods arrive. The warehouse confirms receipt and moves on. Accounts payable processes invoices that arrive and has no visibility of receipts where no invoice ever showed up. The balance is the residue of everything those three teams did not finish, and it accumulates precisely because no one is accountable for draining it.
What the balance should look like
Before diagnosing a GRNI problem, establish what normal looks like. GRNI should approximate the value of goods received during your average invoice lag. If suppliers typically invoice 20 days after delivery and you receive USD 3 million of goods a month, a balance around USD 2 million is structurally correct.
The diagnostic is not the total. It is the ageing profile.
| Ageing bucket | Healthy share of balance | What it means | Action |
|---|---|---|---|
| 0-30 days | 60-75% | Genuine invoices in transit | None, normal timing |
| 31-60 days | 15-25% | Slow suppliers, matching queue backlog | Monitor, chase suppliers |
| 61-90 days | 5-10% | Early-stage exceptions | Investigate by exception |
| 91-180 days | Under 5% | Structural errors | Full investigation required |
| 180+ days | Under 2% | Dead items, almost never real | Clear or write off with approval |
Most organisations that have never actively managed GRNI find 20% to 40% of the balance sitting beyond 90 days. That portion is not a liability in any meaningful sense. It is an error store, and every month it is carried forward, it makes the financial statements less accurate while consuming close capacity.
The Five Things Actually Sitting in an Aged GRNI Balance
Aged GRNI is not one problem. It is five distinct problems that happen to land in the same account, and each requires a different fix. Treating them as a single “chase the invoice” exercise is why the balance never clears.
Over-receipting and quantity mismatch. The warehouse receipts 100 units because that is what the PO said, but 96 arrived. The supplier invoices 96. Four units of value sit in GRNI permanently, because no invoice will ever clear them. This is the single most common cause, and it is invisible at the account level because the residual per line is small.
Unit of measure mismatch. The PO is in cartons, the receipt is in pieces, the invoice is in kilograms. The matching engine cannot reconcile them, the invoice routes to exception, and the receipt stays open. This is endemic in manufacturing and food and beverage, and it is covered in depth in our guide to UoM mismatches in three-way matching.
Invoice paid outside the PO process. The supplier invoice arrives by email, AP cannot find the PO, and it gets processed as a non-PO invoice and paid. The cost is now recorded twice: once through the goods receipt sitting in GRNI, and once through the paid invoice. The expense is overstated and GRNI is a phantom. This is both a control failure and a double-count risk that auditors look for specifically.
Cancelled or short-shipped orders never reversed. An order is part-delivered, the remainder is cancelled, and nobody reverses the open receipt or closes the PO line. The order is commercially dead but accounting-live.
Invoice posted to the wrong PO line. On multi-line orders, an invoice clears line 3 when it should have cleared line 7. Line 7 stays open, line 3 goes negative, and the net account balance looks approximately right while both lines are wrong.
| Root cause | Typical share of aged balance | Correct remedy | Who must act |
|---|---|---|---|
| Over-receipting and quantity variance | 25-35% | Adjust receipt to actual, apply tolerance rules | Warehouse and AP |
| Unit of measure mismatch | 15-25% | Normalise UoM in item master and PO | Procurement and master data |
| Invoice paid as non-PO | 15-20% | Reverse the goods receipt, enforce PO policy | AP and controller |
| Cancelled or short-shipped orders | 15-20% | Close PO line, reverse open receipt | Procurement |
| Wrong PO line matched | 10-15% | Reallocate the invoice to the correct line | AP |
The share breakdown matters because it tells you where to intervene. If a quarter of your aged balance is over-receipting, no amount of supplier chasing will help; you need receipt tolerance rules and a warehouse process change.
Why Manual GRNI Reconciliation Always Falls Behind
Finance teams generally know the balance needs work. What defeats them is arithmetic.
A mid-sized distributor processing 8,000 goods receipts a month with a 95% clean match rate leaves 400 open lines monthly. Investigating one line properly means opening the PO, checking the receipt, searching for a possibly-paid invoice, emailing procurement and waiting for a reply. At fifteen minutes each, that is 100 hours a month, which no AP team has spare during close.
So the work gets deferred, and deferral makes it harder. At 30 days, the buyer remembers the order and the supplier can resend the invoice from live records. At 180 days, the buyer has moved roles, the supplier’s contact has changed, and the item may have been consumed or written off. The investigation cost per line rises while the probability of resolution falls, which is why aged GRNI is self-reinforcing.
This is the same decay curve that makes recovering historical overpayments harder over time, a dynamic we cover in our guide to the accounts payable recovery audit. In both cases the fix is the same in principle: shift detection from a periodic investigation to a continuous control.
| Approach | Lines reviewed monthly | Average age at resolution | Close time consumed | Balance trend |
|---|---|---|---|---|
| Investigate only at year-end | Under 10% | 200+ days | 4-6 days at year-end | Grows steadily |
| Manual monthly review of top values | 20-30% | 90-120 days | 2-4 days per close | Flat to growing |
| Full manual line-by-line review | 100% | 30-45 days | Not sustainable | Falls, then team burns out |
| Automated ageing and exception routing | 100% | 10-20 days | Under 0.5 days | Falls and stays low |
Turning GRNI Into a Controlled Balance
The objective is not to reach zero. A zero GRNI balance would mean no goods were received in the period, or that receipts are not being recorded at all, which is worse. The objective is a balance that is small, young and fully explainable.
Getting there requires four changes.
Age continuously, not at close. GRNI ageing should run weekly against live data, not as a close-week extract. Exceptions surfaced at day 20 are resolvable; the same exceptions at day 120 are archaeology.
Classify root cause automatically. The investigation bottleneck is diagnosis, not action. An agent that can compare receipt quantity to PO quantity, check for a same-vendor same-value paid invoice, and test for UoM inconsistency resolves the diagnosis in seconds, leaving humans to handle only genuine judgement calls.
Route exceptions to the function that can act. Over-receipting goes to the warehouse. Dead orders go to procurement. Wrong-line matches go to AP. Sending everything to AP guarantees a queue, since AP can only fix one of the five root causes.
Chase suppliers automatically. A meaningful share of genuinely young GRNI is simply a missing invoice. Automated supplier chasing at day 15 and day 30, through the vendor portal, clears these before they age into the problem buckets.
Strong purchase order compliance and disciplined PR-to-GRN process design prevent much of this upstream, while accurate GRNI feeds directly into the wider month-end close automation effort. On the standards side, the completeness assertion that drives auditor focus here is grounded in liability recognition principles set out by the IFRS Foundation and reinforced in guidance from the IFAC and the Institute of Management Accountants. Practical treatment of GR/IR mechanics is documented by SAP, and the broader control expectations are summarised well by Corporate Finance Institute and Deloitte.
How Peakflo Helps
Peakflo treats GRNI as a live control rather than a close-week investigation. Its AI agents age every open goods receipt line continuously, then classify the root cause automatically by comparing receipt quantity against PO quantity, testing for unit of measure inconsistency, and searching paid non-PO invoices for the same vendor, value and period to detect phantom balances before they are accrued a second time.
Exceptions route to the function that can actually resolve them, with over-receipting going to the warehouse, dead orders to procurement and mismatched lines to AP, while suppliers are chased automatically for genuinely missing invoices. Because this runs on the same platform as two-way and three-way matching, invoice capture and procurement, with native connectors to systems such as NetSuite and SAP, the accrual that reaches the ledger is a validated residual rather than a negotiated estimate. To see your own GRNI ageing profile analysed, request a demo.
Our Verdict: Fix the Ageing Profile, Not the Total
After analysing how GRNI balances form and persist, here is our recommendation.
Treat GRNI as urgent if
- More than 10% of the balance is older than 90 days
- The balance has grown for three consecutive quarters without receipt volume growing
- Auditors have raised completeness of liabilities in the last two cycles
- Close regularly stalls on accrual disputes between finance and procurement
- You operate multiple entities or ERPs, where reconciliation effort multiplies
Monitor rather than intervene if
- The balance tracks receipt volume closely and ages out within 45 days
- Under 5% of value sits beyond 90 days
- Exceptions already route automatically to procurement and the warehouse
Do not attempt a manual cleanup if
- Open exception lines exceed roughly 200 per month, where manual investigation cannot keep pace
- Root causes are unknown, since clearing without diagnosis guarantees the balance rebuilds
Our Recommendation: Start with ageing, not with clearing. Extract the balance by line, bucket it by receipt date, and sample twenty aged lines to establish the root cause mix. That single exercise tells you whether you have a supplier invoicing problem, a warehouse receipting problem or a PO compliance problem, and those three demand entirely different responses. Clearing the balance before diagnosing the mix is the most common mistake, and it guarantees the same investigation next year.
Conclusion
GRNI is the closest thing finance has to an objective accrual, built from real transactions with real evidence attached. When it becomes a source of month-end argument, that is a signal that the underlying procure-to-pay process is leaking, not that the accounting is hard.
The aged portion of the balance is the diagnostic. Every line older than 90 days represents a specific operational failure that has already happened and been recorded: goods counted incorrectly, an order cancelled without closure, an invoice paid around the PO process. Clearing those lines recovers accuracy in the financial statements, and classifying them tells you exactly which upstream control to fix.
The practical starting point takes an afternoon. Pull the balance by line, age it into buckets, and calculate what percentage sits beyond 90 days. If that number exceeds 10%, the close problem you have been managing every month is not an accounting problem at all.
Frequently Asked Questions
What does GRNI mean?
GRNI stands for goods received not invoiced. It is the accounting balance representing goods or services a business has received but for which the supplier invoice has not yet arrived or has not yet been matched. In SAP environments the equivalent account is usually called GR/IR, meaning goods receipt and invoice receipt clearing.
Is GRNI an asset or a liability?
GRNI is a liability. When goods are received, inventory or expense is debited and the GRNI clearing account is credited, recognising that the business owes the supplier even though no invoice exists yet. It sits on the balance sheet as an accrued liability until the invoice arrives and clears it into accounts payable.
What is a healthy GRNI balance?
A healthy GRNI balance is roughly equivalent to the value of goods received during your average invoice lag, typically 15 to 30 days of receipt volume. If the balance materially exceeds that, or if more than 10% of it is older than 90 days, the account is accumulating structural errors rather than normal timing differences.
Why does the GRNI account keep growing?
GRNI grows when items enter but never leave. The usual causes are over-receipting, unit of measure mismatches between the PO and the receipt, invoices posted against the wrong PO line, cancelled or short-shipped orders where the receipt was never reversed, and invoices processed as non-PO payments while the goods receipt stays open forever.
What is the difference between GRNI and an accrual?
GRNI is a system-generated balance driven by actual goods receipt transactions, so it is evidence-based. A manual accrual is an estimate made by finance for costs incurred without either a receipt or an invoice. Well-run organisations rely on GRNI for received goods and reserve manual accruals for services and costs that never generate a receipt.
How do you clear an aged GRNI balance?
Investigate each aged line individually. Check whether the invoice was paid outside the PO process, whether the goods were actually received, whether the quantity or unit of measure is wrong, and whether the order was cancelled. Reverse erroneous receipts, close dead PO lines, and only write off the residual once procurement has confirmed no invoice is coming.
Can you write off GRNI balances?
Yes, but only after investigation and with documented approval. Writing off aged GRNI without establishing the cause is dangerous because it can release a real liability the supplier will eventually invoice, creating a prior-period issue. Write-offs should follow a formal policy with value thresholds and sign-off, and the root causes should be fixed.
How does GRNI affect the month-end close?
GRNI directly determines reported liabilities, cost of goods sold and margin. If it is wrong, the close is wrong. Teams with uncontrolled GRNI typically spend two to four days of every close investigating the balance and defending it to auditors, which is time that should be spent on analysis.
Why do auditors focus on GRNI?
Auditors focus on GRNI because it is the primary indicator of completeness of liabilities, one of the highest-risk financial statement assertions. A large or aged GRNI balance suggests either that real liabilities are unrecorded or that the balance contains items that should have been cleared, both of which misstate the balance sheet.
How does three-way matching relate to GRNI?
Three-way matching is what clears GRNI. When the purchase order, goods receipt and invoice agree, the invoice posts and the GRNI entry reverses. GRNI is therefore the accumulated population of receipts that matching has not yet resolved, which makes match failure rates and GRNI ageing two views of the same underlying problem.
What is GR/IR clearing in SAP?
GR/IR clearing is the SAP account that holds the difference between goods receipts and invoice receipts against purchase orders. It performs the same function as a GRNI account, and SAP provides dedicated transactions for analysing and maintaining it. Persistent GR/IR residuals usually indicate quantity or price variances rather than genuine timing lags.
Can GRNI reconciliation be automated?
Yes. Ageing, root-cause classification, matching aged receipts against paid non-PO invoices, chasing suppliers for missing invoices and routing exceptions to procurement can all be automated. This converts GRNI from a month-end investigation into a continuously maintained balance, and it is the single highest-leverage fix for teams whose close is dominated by accrual disputes.