GRNI Reconciliation in Manufacturing: Practical Guide

Learn how to reconcile manufacturing GRNI balances by tracing receipts, invoices, PO history, and variances before month-end close.

Published
Updated
Reading Time
11 min
Topics:
Industry GuidesManufacturingGRNI reconciliationGR/IR clearingmonth-end close

GRNI or GR/IR reconciliation in manufacturing is the work of matching materials that have already been received and posted to inventory or accrual accounts against the supplier invoices and purchase order records that should clear those balances. Open items appear when the receipt and invoice do not line up on timing, quantity, price, unit of measure, freight, or receiving accuracy. A useful review ties together PO numbers, receipt dates, invoice dates, quantities, prices, and exception notes so AP, receiving, procurement, and the controller can decide whether to clear the item or keep an accrual in place for month-end.

That is why open GRNI balances are never just an accounting nuisance. In a plant environment, goods can arrive in stages, invoices can trail the receipt by days or weeks, and materials may already be consumed while finance is still waiting for billing support. Some goods received not invoiced manufacturing balances are perfectly normal cutoff items at period end. Others signal a mismatch that will keep rolling forward until someone traces the document trail back to the receipt, invoice, and PO history.

This guide treats GRNI reconciliation in manufacturing as a document-driven investigation, not an ERP feature tour. The goal is to identify what happened on each line, who owns the next action, and which balances belong in the current close versus the exception queue.


Why GRNI Balances Stay Open After Period End in Manufacturing

Manufacturing creates more open GRNI positions than simpler indirect-spend environments because the physical flow of materials rarely moves in lockstep with the paperwork. A receipt can be booked the moment a shipment reaches the dock, while the supplier invoice arrives later, comes in a different unit of measure, or includes charges that were not visible on the original purchase order. If the plant needs the material immediately, production may consume it before AP has the bill that should clear the liability.

For manufacturing month-end accrual reconciliation, the first distinction is whether the item is a normal timing difference or a broken process. A current-period receipt with no invoice yet may belong in accrued liabilities until the vendor bills. An item that is sixty or ninety days old usually points to something else: the wrong receipt quantity, a disputed price, freight billed separately, or a receipt that was posted incorrectly. A goods received not invoiced balance at month end in manufacturing can be valid, but it should never remain unexplained.

Manufacturing also adds complexity that service businesses do not face. The receipt may be booked against a partial delivery, quality may still be under review, conversion between stocking units and invoice units may happen outside AP, and raw materials may already be consumed or issued to production before the supplier paperwork is complete. Each of those realities can leave a legitimate operational trail but an incomplete accounting trail, which is why controllers need the investigation to stay tied to source documents rather than assumptions.

ERP reports help surface the symptom, not the root cause. In SAP and similar systems, GR/IR monitoring can show that a balance is open and aging, but the real answer still sits in the supporting documents and the context around the transaction. That is why finance teams struggle when they treat the report as the investigation. The report tells you where to look. The receipt record, invoice, vendor communication, and PO history explain why the balance is still there.


The Mismatch Patterns Behind Aged GRNI Items

An open GR/IR balance investigation usually lands in a small number of repeatable mismatch patterns. If you can sort the backlog into those buckets quickly, you can assign work faster and stop treating every old item as a one-off mystery.

  • Partial receipt or staged delivery: The plant posts one receipt now and another later, but the supplier invoice covers the full shipment or arrives before the final receipt is booked.
  • Invoice timing lag: Goods are received on time, but the vendor invoice arrives after close or gets routed slowly through AP, leaving an open accrual that may be normal for a short period and problematic if it ages.
  • Price variance: The invoice price does not match the purchase order or the agreed change, so the system leaves a residual balance even though the goods arrived.
  • Freight, duty, or surcharges billed separately: The material line clears, but extra charges show up on a different document or later invoice and keep the item open.
  • Unit-of-measure mismatch: Receiving books cases, AP sees individual units, and the extension does not reconcile even though the physical goods and commercial terms are correct.
  • Receiving or master-data error: The goods received note was posted with the wrong quantity, wrong line, or wrong location, which turns a routine three-way match into a manual cleanup exercise.

When you review the backlog, tag each item with one primary mismatch code first. That stops the report from turning into a collection of anecdotes and makes it easier to see whether the biggest issue sits with one supplier, one plant, one buyer, or one data rule.

The classic goods receipt invoice mismatch in manufacturing usually sits at the boundary between receiving discipline and AP review. That is why aged GRNI cleanup often starts with the same root causes behind manufacturing three-way matching exceptions and tolerance checks, even though the close team discovers them later. The practical question is not just whether the documents disagree, but which document is wrong, incomplete, or still missing.


Build the Investigation Sheet Before You Try to Clear the Balance

Before you clear anything, build one investigation view for each open item. Teams lose days when the review depends on toggling between ERP screens, PDF invoices, receipt records, emails, and vendor statements with no shared line of sight. The same document sprawl is behind many common invoice processing bottlenecks in manufacturing AP.

At a minimum, your investigation sheet should include:

  • supplier name
  • PO number and line number
  • receipt number and receipt date
  • invoice number and invoice date
  • quantity received and quantity invoiced
  • unit of measure
  • unit price and extended amount
  • freight, duty, tax, or other additional charges
  • currency
  • item or line description
  • current owner, dispute status, and next action

Each column should answer a decision question. Receipt and invoice dates tell you whether the issue is cutoff timing or true aging. Quantity received versus quantity invoiced shows whether the problem sits with receipt posting, supplier billing, or partial shipment handling. Unit-of-measure fields expose conversion errors that never appear if the team only compares totals. Price, freight, and tax fields reveal whether the balance sits in the material line or in a later commercial adjustment. Owner and status fields keep the item from disappearing back into a shared queue after the first review.

The supporting document pack matters just as much as the fields. You need the invoice, the receipt record, purchase order history, vendor statement if one exists, and any receiving comments or discrepancy notes that explain what happened on the dock or in the system. That is the evidence that tells you whether you are looking at normal received not invoiced inventory accruals or an exception that should have cleared already.

If your main bottleneck is gathering invoice data into a usable file, AI invoice data extraction for GRNI reconciliation can help build that investigation sheet. Invoice Data Extraction can pull invoice fields, line items, PO numbers, tax amounts, and source file and page references from mixed supplier PDFs and images into Excel, CSV, or JSON, and the same workflow can be used on vendor statements when you need supporting detail for follow-up.


Assign the Work So Open GRNI Items Actually Get Cleared

Good manufacturing GRNI reconciliation depends on clear ownership. When every aged item sits in a shared queue with no next action, accrued liabilities linger because each team assumes someone else has the missing answer. That is not just an internal frustration. CFO.com reported in April 2025 that 50% of finance teams take six or more business days to close the books each month, and 56% said cross-team dependencies prevent faster closes, according to CFO.com's 2025 reporting on month-end close bottlenecks.

Use the mismatch pattern to route the work:

  • AP: Confirm whether the invoice exists, whether it was received but not posted, whether the line values match the PO, and whether the balance is a timing item or a true exception.
  • Receiving or operations: Confirm whether the goods actually arrived, whether the receipt was partial, and whether quantities, dates, or units were posted correctly.
  • Procurement: Resolve price disputes, missing credits, freight terms, supplier follow-up, and any commercial issue that AP cannot settle from the documents alone.
  • Controller or close owner: Review aging, decide whether the accrual remains appropriate, and enforce escalation rules for old balances that should not roll into another close.

The handoff works better when the aging report is reviewed in a short cadence instead of only at month-end. Even a fifteen-minute close huddle around open-item counts, oldest balances, and blocked vendor issues gives each team a defined list to clear before finance starts booking late adjustments. What matters is not a new meeting for its own sake, but a visible owner, a due date, and a reason code that tells the next reviewer why the balance is still open.

This division matters because the same symptom can imply different actions. An invoice dated after period end may need no correction at all beyond keeping the accrual. A price variance may require procurement evidence. A wrong receipt quantity may need receiving to reverse and repost the transaction. The faster you sort those paths, the faster GRNI items come off the aging report.


Separate Current-Period Accruals From Aged Exceptions at Close

A late supplier invoice accrual in manufacturing should not be handled the same way as an item that has been open for several periods. The first may be a routine cutoff matter. The second usually needs correction, escalation, or both. A disciplined close review starts by separating those two populations before anyone starts clearing balances blindly.

For each open item, work through a short decision path:

  1. Keep the accrual: Use this when the receipt is valid, the goods were received in the current period, and the invoice has not arrived yet.
  2. Clear against a newly arrived invoice: Use this when the supplier bill is now in hand and the quantities and prices reconcile.
  3. Correct the receipt or match data: Use this when quantities, dates, or units were posted incorrectly.
  4. Reverse and repost or adjust pricing support: Use this when the accounting entry is wrong even though the commercial activity is real.
  5. Escalate to procurement or the supplier: Use this when the item reflects an unresolved dispute, missing credit, freight issue, or unsupported invoice.

This is where evidence matters. Receipt dates, invoice dates, quantity comparisons, pricing support, freight documentation, and dispute notes should tell you whether the balance belongs in the current close or the exception queue. Many teams also find it useful to flag items by age and status, for example current-period timing, waiting on invoice, waiting on receiving correction, waiting on supplier response, or ready to clear. That keeps a late bill from being treated like an aged process failure. If your process for this step is weak, review your month-end cutoff steps for late supplier invoices alongside the open GR/IR balance investigation so cutoff items and stale exceptions do not get mixed together.


Controls That Keep GRNI From Rebuilding Next Month

Once the current backlog is under control, the real win is reducing how much comes back next period. The most useful controls are the ones tied to the mismatch patterns you actually saw during the reconciliation, not generic close advice copied from another environment.

  • Tighten receipt discipline so the goods received note reflects what physically arrived, when it arrived, and which PO line it belongs to.
  • Review three-way matching tolerances and exception-routing rules for the mismatch types that created the most aged items.
  • Standardize unit-of-measure governance across purchasing, receiving, and AP so conversions do not create avoidable residual balances.
  • Set rules for freight, duty, and surcharge handling so those charges do not sit outside the original purchase order logic with no owner.
  • Add aging thresholds and escalation paths, for example vendor follow-up after a defined number of days and controller review before the item rolls into another close.
  • Run a short post-close review that classifies each old item as normal timing, preventable process failure, master-data issue, or supplier dispute.

Those controls do more than clean up the next month-end accrual reconciliation. They help the team decide where to improve receiving, purchasing, or invoice capture so fewer GRNI items reach the aging report in the first place. Over a few closes, that history also tells you whether the backlog is mostly supplier timing, dock discipline, master-data quality, or approval delays, which makes the next improvement cycle much more precise.

About the author

DH

David Harding

Founder, Invoice Data Extraction

David Harding is the founder of Invoice Data Extraction and a software developer with experience building finance-related systems. He oversees the product and the site's editorial process, with a focus on practical invoice workflows, document automation, and software-specific processing guidance.

Editorial process

This page is reviewed as part of Invoice Data Extraction's editorial process.

If this page discusses tax, legal, or regulatory requirements, treat it as general information only and confirm current requirements with official guidance before acting. The updated date shown above is the latest editorial review date for this page.

Continue Reading

Extract invoice data to Excel with natural language prompts

Upload your invoices, describe what you need in plain language, and download clean, structured spreadsheets. No templates, no complex configuration.

Exceptional accuracy on financial documents
1–8 seconds per page with parallel processing
50 free pages every month — no subscription
Any document layout, language, or scan quality
Native Excel types — numbers, dates, currencies
Files encrypted and auto-deleted within 24 hours