How to Build a Finance Department Goods Received Not Invoiced Clearing Process That Prevents Accrual Buildup

The goods received not invoiced account sits at a busy intersection between purchasing, receiving, and accounts payable. When a company receives goods before the vendor invoice arrives, accounting records a debit to inventory or expense and a credit to the GRNI accrual. The expectation is that the matching invoice will arrive shortly and clear the balance. In practice, invoices arrive late, purchase orders get partially filled, vendors rebill under different numbers, and the GRNI account gradually fills with items that nobody owns or monitors. Left unattended, it becomes one of the more difficult accrual accounts to defend during an audit or year-end close.

Building a deliberate clearing process changes that dynamic. The goal is not to eliminate the account but to give every open balance a defined path to resolution before it ages into a problem.

Understand What Belongs in GRNI and What Does Not

Before designing a workflow, the team needs agreement on what the account is actually supposed to hold. GRNI should contain only valid, temporary timing differences: goods or services have been received and accepted, but the vendor invoice has not yet been processed. It should not contain disputed receipts, duplicate entries, inventory write-off candidates, or amounts that accounting is using as a holding area while ownership questions get resolved.

If the account contains items outside that narrow definition, clearing those first is worth the effort. A one-time cleanup creates a clean baseline, and the ongoing process becomes much easier to manage once the population is accurate.

Assign Clear Ownership

GRNI is frequently nobody's primary responsibility. Purchasing assumes accounts payable is monitoring it. Accounts payable assumes purchasing will follow up with vendors. Controllers discover the problem when auditors ask about the balance.

A functional clearing process requires a named owner, typically within accounts payable or the broader procure-to-pay function, who runs the aging report on a defined schedule, escalates exceptions, and reports status to the controller. Without a named owner, the account drifts.

Establish an Aging Policy Before Items Are Even Created

One of the most effective controls is a written aging policy that defines when a GRNI item should be escalated and when it should be reversed. A reasonable structure for many organizations might look like this:

• Items under 30 days old are monitored but no action is required beyond normal matching.
• Items between 31 and 60 days trigger a vendor inquiry or a check with the purchasing team on whether the goods were truly received as recorded.
• Items over 60 days require a documented decision: either reverse the receipt if goods were not actually received, process an accrual entry if the liability is real but the invoice is delayed, or escalate for formal resolution.

The specific thresholds will vary based on the organization's industry, vendor payment terms, and the typical invoice cycle. The important thing is that thresholds exist and are enforced consistently, not applied selectively at year-end.

Run a Weekly Aging Report and Act on It

The aging report is the operational tool that makes the policy real. It should show every open GRNI item with the receipt date, the purchase order number, the vendor name, the dollar amount, and the number of days outstanding. Sorting by age and by dollar amount helps the owner prioritize where to spend time.

For high-dollar items, a brief weekly review call between accounts payable and purchasing can resolve most open items quickly. Purchasing often knows whether a vendor has shipped everything, whether a partial shipment is expected, or whether the original receipt was entered in error. That information does not naturally flow into accounts payable unless someone asks.

Coordinate With Purchasing on Receipt Accuracy

Many GRNI items age because the receipt was recorded incorrectly at the warehouse level. A receiver enters a quantity of 100 when only 85 units arrived. Accounts payable receives an invoice for 85 and cannot match it cleanly. The GRNI balance for the remaining 15 units sits open indefinitely.

Fixes at the receiving end prevent these items from ever entering the aging bucket. Periodic training with warehouse or receiving staff on the importance of accurate receipt quantities, and a process for correcting receipts promptly when errors are found, reduces the population of stubborn items that frustrate accounts payable.

Handle Vendor Statement Reconciliations Alongside GRNI

Vendor statement reconciliations are a natural complement to GRNI clearing. When accounts payable reconciles a vendor's statement, open GRNI items for that vendor become visible immediately. If the vendor shows an outstanding invoice that accounts payable has not received, the accounts payable team can request a copy and clear the GRNI at the same time. Linking these two activities reduces duplicate effort and accelerates resolution.

Define a Reversal Protocol for Items That Cannot Be Resolved

Some items will not resolve through vendor follow-up. The goods may have been returned, the purchase order may have been cancelled after receipt, or the vendor may have issued a credit that accounting has not yet applied. For these items, a formal reversal process is necessary.

The reversal protocol should require documentation: who approved the reversal, what the original transaction was, and what happened to the underlying goods or liability. A reversal without documentation creates a different audit problem. Reversals with clean support demonstrate that the team is actively managing the account rather than avoiding it.

Report GRNI Status to the Controller at Each Close

At period-end close, the controller should receive a summary of the GRNI balance that shows the total, the aged breakdown, any items over the threshold that remain unresolved, and the disposition plan for significant open items. This positions GRNI as a managed balance rather than an unexplained liability.

If auditors ask about the account during fieldwork, that summary documentation, combined with the aging policy and the weekly clearing records, provides exactly the kind of evidence that shortens conversations and builds confidence in the team's controls.

A Practical Starting Point for Teams Without a Current Process

For teams building this process from scratch, a reasonable first step is to pull the current GRNI balance, sort it by age, and identify every item over 60 days. Working through that population with purchasing creates immediate value and surfaces the specific breakdowns, whether receipt errors, vendor communication gaps, or policy questions, that the ongoing process needs to address.

Building the aging report template, assigning the owner, and writing a one-page policy that defines thresholds and reversal criteria can typically happen within a single period. The discipline of running the report weekly and acting on exceptions is what converts the policy into a genuinely clean account over time.