When inventory value looks wrong after purchasing activity in Cin7 Core, the issue is not always the report, the integration, or something finance can safely correct with a journal. Often, it starts with a timing gap: goods are received before the supplier invoice is processed, or the supplier invoice is authorised before the goods are physically received.

GRNI, or Goods Received Not Invoiced, and GINR, or Goods Invoiced Not Received, are ledger control points designed to bridge operational and financial timing differences. They sit between warehouse activity, supplier invoicing, inventory value, and the general ledger.

A purchase is not one event. It moves through purchase order creation, stock receipt, supplier invoice authorisation, clearing account movement, inventory valuation, accounting sync, and month-end reconciliation. When those events do not clear cleanly, inventory value can drift away from the balance sheet. The warehouse may think stock is correct, while finance sees unresolved clearing balances, supplier liability issues, or differences between Cin7 Core and Xero or QuickBooks Online.

The real question is not only, “Was the stock received?” It is: Did Cin7 Core, the purchase workflow, Accrued Inventory configuration, Account Mapping, and the accounting system all agree on what happened and where the value belongs?

TL;DR

GRNI usually appears when goods are received before the supplier invoice is processed. In Cin7 Core, the accounting treatment depends on whether Accrued Inventory is active.

GINR usually appears when a supplier invoice is authorised before goods are fully received.

These timing gaps can be normal temporarily. They become risky when clearing balances stay open, purchase orders remain unresolved, accounts are mapped incorrectly, or the accounting platform rejects a transaction because the target period is locked.

Manual journals in Xero or QuickBooks may make the Inventory Control Account Asset Balance look correct, but they do not correct Cin7 Core’s transactional sub-ledger.

To diagnose the issue, review the purchase workflow, Accrued Inventory configuration, GRNI / GINR clearing balances, Account Mapping, Cin7 Core Stock on Hand Value, and the GL Inventory Control Account Asset Balance together.

What Does GRNI Mean in Cin7?

GRNI means Goods Received Not Invoiced. It usually appears when stock has been received into Cin7 Core, but the supplier invoice has not yet been processed or matched.

When Accrued Inventory is active, receiving stock before the invoice is processed can create this accounting movement:

Debit: Inventory Asset Account
Credit: Accrued Inventory / GRNI Clearing Account

This updates operational stock at the estimated purchase order value while the supplier invoice is still outstanding. When the supplier invoice is later authorized, Cin7 Core should clear the GRNI balance through:

Debit: Accrued Inventory / GRNI Clearing Account
Credit: Accounts Payable

GRNI is not always an error. It can be a normal interim state. The risk appears when the purchase order, receipt, supplier invoice, or delivery discrepancy remains unresolved, leaving a stale un-cleared sub-ledger variance rather than a temporary timing difference.

What Does GINR Mean in Cin7?

GINR means Goods Invoiced Not Received. It usually appears when the supplier invoice is authorized before the goods are physically received, such as when an overseas supplier requires invoice authorization or payment before cargo arrives.

In that case, Cin7 Core may record:

Debit: Goods Invoiced Not Received (GINR) Account
Credit: Accounts Payable

At this point, the value does not hit the Inventory Asset ledger because the stock has not yet arrived in a warehouse bin location. When the freight arrives and the warehouse authorizes the Stock Received step, Cin7 Core should close the loop through:

Debit: Inventory Asset Account
Credit: Goods Invoiced Not Received (GINR) Account

GINR is not automatically wrong. It becomes a problem when the goods are never fully received, the purchase order remains open, or the clearing account is not resolved.

The financial impact also needs careful interpretation. When GINR is mapped correctly to an asset-based clearing control code, the overall footprint of the balance sheet expands, but net working capital calculations remain accurate, avoiding an artificial distortion of true business net assets. The balance still needs to clear. If it does not, the business can carry stale clearing balances that make inventory and supplier reporting harder to trust.

When a Timing Gap Becomes an Inventory Valuation Problem

A timing gap is not automatically a valuation problem. Many businesses receive goods before the invoice arrives. Many suppliers invoice before stock is received. In those cases, GRNI and GINR are useful clearing mechanisms.

The problem begins when the timing gap stops being temporary. Common triggers include purchase orders left open after partial receipt, supplier invoices authorized against incomplete receipts, split invoices that do not match received quantities cleanly, delivery discrepancies that are never resolved, Accrued Inventory configuration that does not match the workflow, Account Mapping that routes values into the wrong clearing or asset accounts, late invoice cost changes posted into a locked accounting period, or manual journals used to force the GL to match without correcting Cin7 Core.

At that point, the issue is no longer just “received vs invoiced.” It becomes a valuation and control issue. Cin7 Core may show one version of inventory value, while the accounting system shows another. The difference may sit inside stale clearing balances, cost variance entries, or un-reconciled sub-ledger variances.

The better month-end question is not, “Why does Cin7 not match Xero or QuickBooks?” It is, “Where did the purchase workflow stop matching the financial workflow?”

The Configuration Layer: Account Mapping and Accrued Inventory Setup

This issue should not be described as “purchase method mapping.” In Cin7 Core, Purchase Method relates to document sequencing logic, such as Stock First or Invoice First. The ledger trigger behavior is governed by Accrued Inventory configuration and Account Mapping.

Accrued Inventory configuration determines whether GRNI / GINR clearing entries are created in the expected way. Account Mapping determines where those values land in the accounting system. Relevant accounts that require correct mapping include Inventory Asset, Accrued Inventory / GRNI, Goods Invoiced Not Received (GINR), Accounts Payable, Cost Variance, COGS, landed cost accounts, and variance or discrepancy accounts where relevant.

If these accounts are misaligned, the operational transaction may look complete while the financial picture remains unresolved. That is why the issue is not only whether data moved from Cin7 Core into Xero or QuickBooks. It is whether the right transaction moved into the right account, in the right period, with the correct clearing logic behind it.

An integration can execute and still produce confusing financial results if the underlying configuration or workflow state is wrong.

Cin7 Core Sub-Ledger vs GL: Why Manual Journals Do Not Fix the Source

Posting a manual journal directly inside Xero or QuickBooks to force-align the general ledger is a cosmetic fix. It may make the Inventory Control Account Asset Balance look closer at month-end, but it does not correct the Cin7 Core Sub-ledger Valuation.

A manual journal does not change open purchase orders, clear GRNI or GINR, alter the Stock Received state, correct the Invoice tab, update item valuation cards, or repair Cin7 Core transaction history. The next time stock moves, or a previously unsynced historical transaction is pushed, Cin7 Core continues calculating from its own transactional sub-ledger. The variance can reappear because the source data was never corrected.

This does not mean manual journals are never appropriate. It means they are not a substitute for correcting the purchase workflow, clearing account logic, or Cin7 Core sub-ledger source.

A manual journal can adjust the accounting presentation. It cannot repair the operational transaction that created the difference.

Locked Periods, Cost Variance Adjustments, and Accounting Rejections

Another edge case appears when the final supplier invoice cost differs from the original purchase order receipt baseline. This can happen when goods are received at an estimated cost, but the authorised supplier invoice later confirms a different cost.

Cin7 Core handles this through a cost adjustment layer applied to the item’s unique inventory cost card. If the stock is still on hand, that cost adjustment may affect inventory value. If the product has already been sold or fulfilled before invoice authorisation, Cin7 Core can drop a system-generated cost variance journal entry on the current date to adjust the variance downstream.

It does not retroactively rewrite or un-post the original stock receipt ledger entry.

If the supplier invoice authorisation date falls in a period that is already locked in Xero or QuickBooks, the accounting platform may reject the transaction payload. That does not necessarily mean the sync engine failed. It means the accounting system rejected the entry because Cin7 Core was attempting to post into a closed financial period.

The result can be difficult to reconcile: Cin7 Core has updated internally, but the GL does not contain the matching adjustment. This is why locked periods, invoice authorisation dates, cost variance accounts, and inventory valuation need to be reviewed together when purchase-related valuation issues keep appearing.

How to Diagnose GRNI, GINR, and Inventory Valuation Issues

Reports are useful, but no single report explains the full root cause. Use them in sequence.

1. Audit the Financial Transactions vs Stock on Hand Difference Report
   Isolate the cumulative variance boundary between the inventory sub-ledger and the General Ledger. This confirms whether the issue has moved beyond a normal timing gap into a measurable difference between Cin7 Core records and GL asset balances.

2. Analyze the Stock Received vs Invoice Report
   Track down purchase orders with timing gaps between warehouse intake and supplier billing. This helps identify whether the difference is expected, temporary, stale, or structurally unresolved.

3. Scan the Pending Purchase Orders Report
   Filter for open lines with unresolved To Invoice or To Receive values. These open lines may explain why GRNI or GINR balances have not cleared.

4. Deep-dive via Purchase Invoice Details and Inventory Movement Summary Reports
   Evaluate supplier invoice cost differences, cost variance postings, average cost interpretation, FIFO or FEFO valuation behaviour, landed cost treatment, and locked-period accounting rejection.

After reviewing the reports, confirm whether Accrued Inventory is active and whether it matches the business’s intended purchasing workflow. Then review Account Mapping for Inventory Asset, Accrued Inventory / GRNI, Goods Invoiced Not Received (GINR), Accounts Payable, Cost Variance, COGS, landed cost accounts, and relevant variance accounts.

If supplier invoice authorisation happened after the period was locked, check whether the accounting platform rejected the transaction payload. This can leave Cin7 Core updated internally while Xero or QuickBooks lacks the matching journal.

If there was a genuine receiving or invoicing error, do not default to manual stock adjustments. Manual stock adjustments create new cost layers and bypass open purchase orders. That can separate operational stock balances from their matching financial entry points and freeze un-cleared GRNI or GINR balances on the balance sheet.

Where an operational receiving or invoicing error needs to be reversed, the correct principle is to use the native Undo or Void route on the relevant Cin7 Core task card, so the transaction can return cleanly to draft status without breaking sub-ledger integrity. The exact correction path depends on the transaction state and should be validated before action.

When GRNI and GINR Become a Finance and Operations Control Issue

GRNI and GINR problems are rarely just “accounting cleanup.” They often show that finance and operations are not working from the same event sequence.

The warehouse may consider the stock received, while finance still sees an open clearing balance. The GL may show an asset or liability position that does not match the Cin7 Core Stock on Hand Value. The team may start using manual journals or spreadsheets to force agreement.

That is when a timing issue becomes a control issue.

Inventory valuation affects balance sheet accuracy, supplier liability confidence, COGS, margin reporting, replenishment decisions, month-end close confidence, and trust between finance and warehouse teams.

A useful accounting hygiene boundary is the 2% benchmark. If required inventory adjustments consistently exceed 2% of total inventory value, the business may no longer be dealing with normal timing differences. It may have a workflow discipline issue, Accrued Inventory configuration problem, Account Mapping issue, or structural purchasing control problem.

That 2% threshold should be treated as an internal corporate control metric used as a benchmark for process hygiene, not an operational law enforced by Cin7 Core.

The goal is not to make one report balance for month-end. The goal is to restore alignment between receiving, supplier invoicing, clearing accounts, Cin7 Core Stock on Hand Value, and the GL Inventory Control Account Asset Balance.

Need Clarity on Your Cin7 Inventory Value?

If inventory value changes after purchasing activity, the issue may not be the report.

It may be how receiving, supplier invoices, Accrued Inventory configuration, GRNI / GINR clearing accounts, Account Mapping, and the accounting system are aligned.

A Cin7 Inventory Audit & Financial Alignment Review helps trace valuation drift back to its source, clear un-reconciled GRNI / GINR clearing balances, and align warehouse activity with balance sheet reporting.

Restore the Link Between Receiving, Invoicing, and Inventory Value

Received and invoiced are not the same event in Cin7 Core. Goods can arrive before the supplier invoice is authorised. Supplier invoices can be processed before goods reach the warehouse. GRNI and GINR exist to bridge those timing gaps, but those clearing balances are only safe when they clear correctly.

When purchase workflows remain open, Accrued Inventory configuration does not match the workflow, Account Mapping is wrong, cost variance journals are rejected by locked accounting periods, or manual journals are used to force the GL to match, the issue can move from temporary timing difference to persistent valuation drift.

The right question is not, “Why does this report look wrong?” It is, “Where did the receiving, invoicing, clearing account, sub-ledger, and GL sequence fall out of alignment?”

That is the difference between correcting a month-end symptom and restoring trust in the system behind the numbers.

Need Support With Cin7 GRNI, GINR, and Inventory Value Issues?

Learn how Fiskal helps Cin7 Core environments identify the purchasing workflow, Accrued Inventory, Account Mapping, valuation, or accounting issues behind unresolved GRNI / GINR balances.

📞 Or call us directly: (954) 415-7895

Share on your socials.