Written by Marijn Overvest | Reviewed by Sjoerd Goedhart | Fact Checked by Ruud Emonds | Our editorial policy
Goods Received Not Invoiced (GRNI) — Definition, How Does It Work + Best Practices
- Goods Received Not Invoiced (GRNI)means that goods have been received, but the supplier invoice has not yet been issued or recorded. The company has the goods and a real obligation, which is temporarily recorded on a GRNI account.
- GRNI ensures costs and liabilities are recognized in the correct accounting period, even when invoices are delayed. Without GRNI, expenses, inventory, and profit can be misstated.
- GRNI is a temporary account that is cleared once the invoice arrives. The amount is moved from GRNI to Accounts Payable. Unmonitored GRNI balances are a common warning sign of issues in the Procure-to-Pay process.
What is Goods Received Not Invoiced (GRNI)?
Goods Received Not Invoiced (GRNI) refers to a situation where a company has received goods or services, but the supplier invoice has not yet been received or processed.
From an accounting and procurement perspective, this creates a timing gap:
- The business already controls the goods and can use or sell them.
- There is no invoice yet to post the liability to Accounts Payable.
To handle this gap, companies use a GRNI account, which acts as a temporary liability account. It records the value of the received goods until the supplier’s invoice arrives.
This concept is commonly used in accrual accounting and is standard in ERP-driven Procure-to-Pay processes. It helps ensure that costs, inventory, and liabilities are recorded accurately and in the correct period, even when invoicing is delayed.
Why is GRNI Important?
GRNI is important because it ensures that costs and liabilities are recorded in the correct period, even when supplier invoices are delayed.
Without GRNI, companies risk understating expenses, overstating profit, and showing inaccurate inventory and liabilities. By using GRNI, finance and procurement teams keep financial reporting aligned with what actually happened operationally.
How Does GRNI Work?
In a typical Procure-to-Pay process, GRNI appears when there is a timing difference between the physical receipt of goods and the arrival of the supplier invoice.
The process usually starts with a purchase order (PO). Once the goods are delivered, the warehouse or receiving team confirms the receipt in the system. At this point, the company has control over the goods and can use them in operations or sell them further. Because the supplier invoice has not yet been received, the system cannot post the amount to Accounts Payable. Instead, the value of the received goods is recorded on a GRNI account, which represents a temporary liability.
When the supplier later sends the invoice, the finance or accounts payable team reviews and matches it against the purchase order and the goods receipt. After the invoice is approved, the GRNI balance is cleared, and the amount is transferred to Accounts Payable. From that moment, the liability is treated as a normal supplier payable and follows the standard payment process.
In practice, GRNI balances are reviewed regularly, often at month-end closing. Open GRNI items may indicate delayed invoices, quantity or price mismatches, or process issues in the Procure-to-Pay cycle. Keeping GRNI under control helps ensure accurate financial reporting and a smooth collaboration between procurement, warehouse, and finance teams.
10 Best Practices For GRNI
1. Use three-way matching as a standard control
Three-way matching ensures that the purchase order, goods receipt, and supplier invoice align before GRNI is cleared. If this control is weak, GRNI becomes a holding account for unresolved discrepancies.
How to do it:
Extract a list of invoices from the past 90 days that required manual override or tolerance approval. Calculate how many were posted despite price or quantity mismatches. If manual overrides exceed 5 to 10 percent of total invoices, your matching discipline is weak.
Review ERP tolerance settings per spend category. Do not accept a single global tolerance. Define stricter rules for direct materials and high-value purchases. Test the configuration by simulating a quantity or price variance and confirm that the system blocks posting automatically.
Ensure blocked invoices trigger workflow notifications with named ownership, not shared inboxes. Measure two KPIs monthly: invoice first-pass match rate and average days to resolve blocked invoices. This reduces manual intervention, increases invoice accuracy, and results in a measurable decline in GRNI mismatches within one or two reporting cycles.
2. Monitor GRNI continuously, not only during closing
When GRNI is reviewed only at the month-end, issues accumulate and become urgent instead of being controlled.
How to do it:
Every week, extract the full GRNI aging report at the transaction level. Sort first by value, then by aging. Identify the top 15 highest-value items and all items older than 60 days.
Schedule a 30-minute cross-functional review. During the meeting, assign each item a clear owner and deadline. Track progress in a shared action log. Set a control rule: if more than 20 percent of the total GRNI balance is older than 60 days, escalate to P2P leadership immediately. The outcome is a steady reduction of aged balances, smoother month-end closing, and earlier detection of recurring issues.
3. Assign clear ownership for GRNI resolution
GRNI often stagnates because responsibility is unclear.
How to do it:
Analyze at least 100 historical mismatches and categorize them manually into quantity, price, timing, or master data errors. Build a responsibility matrix linking each category to a specific function.
Publish the matrix in your Procure-to-Pay documentation and formally communicate it. Adjust ERP workflow routing so blocked invoices are automatically assigned to the correct department. Track the average resolution time by department monthly. If one department consistently exceeds SLA targets, address it during performance reviews. The outcome is clear accountability, reduced internal delays, and shorter GRNI clearing cycles.
4. Standardize supplier invoicing requirements
Inconsistent supplier invoices generate recurring GRNI discrepancies.
How to do it:
Pull all rejected or blocked invoices from the previous quarter and identify the three most common invoice errors. Update supplier invoicing guidelines to explicitly address those fields.
Send formal communication to suppliers outlining mandatory invoice elements such as PO number, delivery reference, line-level quantities, and agreed price format. Integrate compliance requirements into new contracts. Configure ERP validation rules to automatically reject invoices missing mandatory data. Track supplier compliance rate quarterly and escalate suppliers with repeated errors during business reviews. The outcome is higher invoice quality, fewer processing delays, and a measurable reduction in GRNI exceptions.
5. Actively manage aged GRNI balances
Old GRNI balances distort the balance sheet and increase audit risk.
How to do it:
At the beginning of each month, extract the GRNI aging report and focus exclusively on balances older than 60 or 90 days. Categorize each item into missing invoice, over-receipt, price dispute, or posting error.
Assign corrective action immediately. For items with no operational justification, initiate formal reversal or write-off procedures with documented approval.
Define a control target: aged balances above 90 days should not exceed 5 percent of the total GRNI balance. This improves balance sheet integrity, reduces audit exposure, and strengthens financial discipline.
6. Ensure cross-functional alignment in the Procure-to-Pay process
GRNI performance reflects how well procurement, logistics, and finance collaborate.
How to do it:
Introduce shared KPIs such as invoice first-pass match rate, percentage of GRNI older than 60 days, and average mismatch resolution time. Hold a monthly P2P governance meeting where these metrics are reviewed.
If recurring mismatches originate from specific suppliers, materials, or locations, initiate root cause workshops. Implement corrective actions at the process level, such as improving goods receipt accuracy or updating contract pricing data.
This strengthens cross-functional cooperation and improves overall P2P efficiency.
7. Automate GRNI posting and clearing where possible
Manual journal entries increase error risk and weaken audit trails.
How to do it:
Review how GRNI entries are created in your ERP. Confirm that GRNI is automatically posted at goods receipt and automatically cleared upon successful invoice match.
Generate a report of all manual GRNI journal entries from the past quarter. Identify why they occurred. If manual entries exceed 5 percent of total GRNI transactions, system configuration requires review.
Restrict manual postings to approved finance roles and require documented justification. The outcome is higher consistency in postings, stronger internal controls, and fewer reconciliation discrepancies.
8. Set GRNI tolerance thresholds and approval rules
Improperly calibrated tolerances either block too many invoices or allow excessive risk.
How to do it:
Review historical variance data and determine the typical deviation range by category. Based on materiality, define thresholds for automatic acceptance, managerial approval, and mandatory block.
Configure these thresholds directly in ERP. Track monthly statistics on invoices processed within tolerance versus those requiring approval. If more than 15 percent of invoices require manual approval, tolerance settings may need recalibration.
The outcome is faster invoice processing with controlled financial exposure.
9. Use GRNI trends as a supplier performance indicator
Recurring mismatches may reflect supplier discipline issues.
How to do it:
Generate a supplier-level GRNI report showing frequency of mismatches, average aging, and variance type. Rank suppliers by discrepancy rate. Include these metrics in quarterly supplier scorecards.
For suppliers above threshold levels, agree on improvement actions such as invoice format correction or pricing validation process. Monitor improvement over two reporting cycles. This improves supplier compliance and sustained reduction in GRNI discrepancies.
10. Integrate GRNI controls into month-end closing procedures
GRNI must be formally validated before financial close.
How to do it:
Add the GRNI review as a mandatory step in the month-end checklist. Before closing, verify that aged balances are within defined thresholds and review all manual adjustments posted during the month.
Require formal sign-off from the P2P process owner and finance controller. Document unresolved balances with explanation and action plan.
Archive documentation for audit traceability. The outcome is accurate financial reporting, fewer audit findings, and disciplined closing governance.
10 Key Differences Between GRNI and Accounts Payable
4 Common Challenges of GRNI
6 Benefits of GRNI
Conclusion
Goods Received Not Invoiced (GRNI) is more than an accounting technicality. It is a critical control point that connects procurement, warehouse operations, and finance within the Procure-to-Pay process. By recognizing liabilities at the moment goods are received, GRNI ensures that financial reporting reflects operational reality, even when supplier invoicing is delayed.
When GRNI is poorly managed, it leads to aged balances, manual corrections, audit risks, and friction between teams. When it is well controlled, supported by clear ownership, best practices, KPIs, and ERP automation, GRNI becomes a powerful indicator of process health and discipline.
Frequently asked questions
What is GRNI?
GRNI (Goods Received Not Invoiced) refers to a situation where goods or services have been received, but the supplier invoice has not yet been issued or recorded. The value is temporarily posted to a GRNI account to reflect a real obligation before the invoice arrives.
How does GRNI appear in ERP systems?
In ERP systems, GRNI is created automatically when goods are received against a purchase order without an invoice. It appears as an interim liability in the general ledger and is supported by GRNI aging and reconciliation reports.
What KPIs are used to monitor GRNI?
Common GRNI KPIs include open GRNI balance, GRNI aging, average clearance time, three-way match success rate, exception rate, and month-end GRNI adjustments.
About the author
My name is Marijn Overvest, I’m the founder of Procurement Tactics. I have a deep passion for procurement, and I’ve upskilled over 200 procurement teams from all over the world. When I’m not working, I love running and cycling.
