Join our FREE webinar: Stock Take & Year-End Prep in Cin7 | Wednesday, December 17 at 12PM EST. Click to sign up →

BOOK A CALL

Why Cin7 Inventory Valuation Changes Without New Transactions

Cin7 inventory values shifted and the stock ledger shows nothing. The trigger is in the purchase ledger. Learn the five patterns and how to diagnose which one is active.

SYSTEMS AND SOFTWARE

Jaco Roets

7/12/202616 min read

Why Cin7 Inventory Valuation Changes Without New Transactions

Jaco Roets, Co-founder & CEO @ Fiskal

TL;DR

When Cin7 inventory valuation shifts without a new transaction visible in the stock ledger, the trigger is in the purchase ledger -- not the stock movement history. The physical warehouse layer and the financial costing layer operate independently.
The most common cause is a supplier invoice authorized after the related stock has already been fulfilled to customers. Cin7 cancels the original estimated cost journals and rewrites them using actual FIFO/FEFO costs. No new stock movement is created.
Five distinct patterns cause this. Each has a different trigger location and a different diagnostic path. A manual corrective journal posted directly in Xero or QuickBooks Online does not resolve any of them -- it creates additional system integrity problems.
The three-report diagnostic stack -- the Financial Transactions vs Stock on Hand Difference Report, the Stock Received vs Invoice Report, and the Sync History Log -- is the correct starting point for identifying which pattern is active.
Once the pattern is identified, the finance team faces a defined choice: temporarily unlock the prior period to allow the corrective adjustment to settle cleanly, or absorb the cumulative variance in the current reporting cycle to protect finalized period filings. That decision depends on which pattern is driving the movement.

Why did my Cin7 inventory value change without any new transactions?

Quick Reference: Three Questions Finance Teams Ask First

What is actually causing the COGS adjustment with no stock movement?

Cin7 Core maintains two distinct operational layers. The physical stock movement layer records warehouse transactions: goods receipts, fulfillments, stock transfers. The financial costing layer records the cost distribution of those movements using FIFO, FEFO, or Special actual costing methods.

A change in the financial costing layer does not produce a new entry in the physical stock movement layer. This is designed behaviour.

The most common trigger is a supplier invoice authorized after the related stock has already been sold and fulfilled. When the invoice unit cost differs from the original purchase order estimate, Cin7 cancels the original estimated FIFO/FEFO cost distribution journals and rewrites them using the actual cost. The GL balance changes when this correction syncs. No new stock movement appears because no physical movement occurred.

Can I just post a manual journal in Xero or QuickBooks Online to fix the balance?

Five distinct patterns can produce this result. The pattern active in your system determines where to start the investigation.

Pattern 1: Cost Matching Variances: a supplier invoice is authorized with a unit cost that differs from the original purchase order estimate, after the stock has already been fulfilled.
Pattern 2: Post-Fulfillment Landed Costs: freight, customs duties, or port fees are allocated to a purchase order after the goods have already been shipped to customers.
Pattern 3: GRNI/GINR Clearing Gaps: a variance between the PO receipt estimate and the authorized invoice amount fails to clear through the accrual layer correctly.
Pattern 4: Period Lock Disconnect: the accounting system is locked but the Cin7 Core period lock is left open, or vice versa, allowing operations staff to alter historical transactions after books are finalized.
Pattern 5: Sync Queue Backlog: transactions held in a Pending, Failed, or Warning sync state are cleared in a batch, pushing entries with their original effective dates into accounting periods that have no synchronized lock in place.

Each pattern has a different trigger and a different diagnostic starting point. A single corrective action does not resolve all five.

No. This is one of the most common responses to this problem, and it is a structural system hazard.

Posting a manual journal directly in Xero or QuickBooks Online to force the inventory balances to agree masks the root cause without resolving it. When the next Cin7 sync cycle runs, it pushes the system-generated cost adjustment entry again, creating a duplicate transaction listing in the accounting platform. Over time, this breaks the sub-ledger integrity between Cin7 and the accounting system in ways that are difficult to unpick.

The system-generated cost adjustment journals that are causing the unexplained movement are Cin7 correcting its own FIFO/FEFO cost distribution. Reversing or deleting them without understanding the trigger leaves COGS in an incorrect state.

The Passive Inventory Valuation Shift: What You Are Actually Looking At

A passive inventory valuation shift in Cin7 Core is a change in the reported inventory asset value or COGS figures that occurs without any new stock movement being entered in the system. The balance sheet moves. The P&L moves. The stock movement history does not.

These shifts are substantive financial adjustments. They are not rounding differences and they do not resolve on their own. In most cases they represent a cost correction that Cin7 has calculated correctly, the problem is not that the correction is wrong, it is that the correction is unexpected and untraceable through the standard investigation path.

The scale of the impact depends on the volume of transactions affected and the variance between the original estimated cost and the actual invoiced cost. Fiskal uses a 2% variance threshold as a control health indicator: variances below this level are typically attributable to routine invoice rounding. Variances above it indicate a systemic timing gap in the purchasing or invoicing workflow that requires investigation.

The immediate operational consequence is a month-end close that cannot be completed with confidence. The finance team cannot sign off on figures that include an unexplained movement, and the standard report path returns nothing useful. The investigation stalls because it is starting in the wrong layer.

Two Layers, One Trigger Location

Understanding why this happens requires understanding one structural characteristic of Cin7 Core that is not always visible in day-to-day operations.

Cin7 Core maintains two operationally distinct layers:

The physical stock movement layer records warehouse events, goods receipts, purchase order receipts, fulfillments, stock transfers, stock adjustments. This is what the stock movement history and inventory movement reports reflect.
The financial costing layer records the cost distribution of those physical events,the FIFO/FEFO parcel cost allocations, the COGS journals, the GRNI/GINR accrual entries, and the sync to the accounting platform GL.

These two layers are intentionally decoupled. A physical event in the warehouse layer creates a corresponding entry in the financial costing layer. But a change in the financial costing layer, a cost correction, an invoice variance adjustment, a landed cost reallocation, does not create a new entry in the physical stock movement layer. There is no new receipt, no new adjustment, no visible footprint in the stock movement history.

This is not a design flaw. It is how Cin7 keeps the warehouse operational record separate from the financial valuation record. The problem arises when the timing gap between a physical event (goods received, stock fulfilled) and the corresponding financial event (invoice authorized, landed cost allocated) creates a retroactive cost correction that lands in a period the finance team believes is closed.

The trigger for the unexplained movement is almost always in the purchase ledger. Late supplier invoice authorization is the most common source. Late landed cost allocation is the second. GRNI/GINR clearing account timing failures are the third. In each case, the financial costing layer responds to an event in the purchase ledger, not to a new stock movement.

This is why searching the stock movement history returns nothing. The audit trail for the cost correction does not live there. It lives in the purchase ledger events, the sync history log, and the GRNI/GINR clearing account activity.

The Purchase Ledger Cost Cascade

The following sequence describes the standard system behaviour flow that produces a passive inventory valuation shift. Understanding each step makes the trigger visible.

Step 1: Goods Received, Cost Estimated

Stock arrives against a purchase order. If the supplier invoice has not yet been authorized, Cin7 values the received stock using the purchase order unit price as a baseline cost estimate. This estimated cost is used to record the asset value in the financial costing layer.

Step 2: Stock Fulfilled, COGS Logged at Baseline

The stock is sold and fulfilled to customers. Cin7 logs the Cost of Goods Sold to the accounting integration using the baseline cost from Step 1. At this point the COGS entry reflects the purchase order estimate, not the actual invoiced cost.

Step 3: Invoice Authorized with a Variance

The supplier invoice arrives. When it is authorized in Cin7, the actual unit cost is now known. If it differs from the purchase order estimate used in Step 1, a cost variance exists between what the financial costing layer recorded and what the actual cost turned out to be.

Step 4: FIFO/FEFO Cost Layers Recalculated

Cin7 automatically cancels the original estimated cost distribution journals and rewrites them using the actual FIFO/FEFO unit cost from the authorized invoice. This recalculation propagates through all downstream stock movements, including the fulfilled sales from Step 2, that drew from the affected cost parcel.

Step 5: Corrective Adjustment Synced to GL with Original Effective Date

The corrective adjustment is queued and synced to Xero or QuickBooks Online. Critically, Cin7 applies the original transaction effective date when exporting this entry, not the date the sync runs. If the accounting period that corresponds to the original transaction date is still open, the GL balance sheet changes immediately when the sync executes.

This is the mechanism that makes prior accounting periods vulnerable even after the finance team believes a month is closed. The GL is only protected if the corresponding period lock is in place in both Cin7 and the accounting platform simultaneously.

Step 6: Finance Team Sees GL Balance Change, No Warehouse Movement

The finance team opens the GL inventory account or the COGS report and sees the balance has changed. They search the stock movement history in Cin7. Nothing new appears. The trigger for the change was the invoice authorization in Step 3, which is a purchase ledger event, not a warehouse event. The audit trail for the change lives in the Financial Transactions vs Stock on Hand Difference Report and the Sync History Log, not in the stock movement history.

The Five Patterns That Trigger Passive Inventory Valuation Shifts

The Purchase Ledger Cost Cascade describes the general mechanism. Five distinct operational patterns trigger it. Each has a different origin, a different system layer, and a different diagnostic path. Knowing which pattern is active determines both the correct investigation approach and the correct resolution decision.

Trigger: Transactions held in a Pending, Failed, or Warning sync state are cleared in a batch, pushing old entries into the GL simultaneously.

System layer: Integration bridge and API execution layer

What happens: When a sync queue backlog clears, typically after resolving a failed account mapping, correcting an authorization error, or manually retrying failed entries, all queued transactions export to Xero or QuickBooks Online with their original transaction effective dates. Cin7 does not stamp these entries with the date the sync actually ran. If the accounting periods corresponding to those original dates are still open, the GL balance sheet changes immediately across multiple historical periods simultaneously. The finance team sees several periods move at once with no recent corresponding activity in Cin7.

Diagnostic indicator: The Sync History Log shows a cluster of historical-dated entries posting within a short time window. The affected GL accounts show movements across multiple prior periods. There is no single new transaction in Cin7 that explains the change.

Pattern 1: Retroactive FIFO/FEFO Re-Allocation from Cost Matching Variances

Pattern 2: Post-Fulfillment Landed Cost Adjustments

Trigger: A supplier invoice is authorized with a unit cost that differs from the original purchase order estimate, after the associated stock has already been fulfilled to customers.

System layer: FIFO/FEFO costing distribution layer

What happens: Cin7 cancels the original estimated cost distribution journals and rewrites them using the actual invoice cost on a FIFO/FEFO basis. The GL correction syncs to Xero or QuickBooks Online during the next sync interval, using the original transaction effective date.

Diagnostic indicator: The Financial Transactions vs Stock on Hand Difference Report shows a cost correction entry dated to the original receipt or fulfillment period. The Stock Received vs Invoice Report shows a variance between the PO price and the authorized invoice price for the affected product.

Pattern 3: Unreconciled GRNI/GINR Clearing Account Gaps

Trigger: Freight, customs duties, port fees, or other landed costs are allocated to a purchase order after the goods from that order have already been shipped to customers.

System layer: GL integration and manual journal layer

What happens: The landed cost adjustment journal uses the authorization date of the cost event as its effective date. If the accounting period for that date is still open, the GL inventory asset balance and COGS figures change. Importantly, this adjustment does not alter historical warehouse physical quantities. Only the financial costing layer is affected. This creates a temporary reporting variance between the stock movement summary (which still reflects the original quantity and original unit cost) and the GL asset balance (which now reflects the adjusted cost).

Diagnostic indicator: The GL journal date for the landed cost adjustment will not match any stock movement date. The Inventory Movement Details Report will show the original unit cost while the GL COGS account reflects the adjusted amount. This variance persists until the adjustment syncs fully.

Pattern 4: Period Lock Disconnect Between Cin7 and the Accounting Platform

Trigger: A variance between the estimated purchase order receipt price and the final authorized invoice amount fails to clear correctly through the Goods Received Not Invoiced or Goods Invoiced Not Received accrual layer.

System layer: Inventory accrual and clearing account layer

What happens: When inventory accrual is active, stock received against a purchase order is initially posted to the GRNI or GINR clearing account at the estimated PO price. When the invoice is authorized, the clearing account should reverse and the actual cost should flow to the GL inventory control account. If the accounting period is closed too early, before Cin7 has had the opportunity to post the clearing reversal, the variance remains trapped in the accrual account rather than flowing correctly to COGS and the inventory asset account.

Diagnostic indicator: The GRNI or GINR clearing account carries a balance into the next period. The Financial Transactions vs Stock on Hand Difference Report shows a discrepancy between the physical warehouse valuation and the GL inventory balance that cannot be traced to a new transaction.

Pattern 5: Sync Queue Backlogs Processing Retroactively

Trigger: The accounting system is locked by the finance team but the corresponding period lock inside Cin7 Core is left open, or the reverse, Cin7 is locked but the accounting platform remains open. Operations staff continue to alter historical transactions, invoices, or stock definitions within Cin7 after the GL books are finalized.

System layer: Compliance and accounting governance layer

What happens: When an active period lock date is configured in Cin7 Core, it hard-blocks any transaction creation, editing, or deletion prior to that date across the entire platform. For Xero and QuickBooks Online integrations, Cin7 is designed to sync lock parameters between the platforms. If a backdated transaction predates the synchronized lock date, Cin7 marks the sync status as Failed to preserve ledger integrity. The vulnerability is the gap between when the GL is locked and when the corresponding Cin7 lock is set.

Diagnostic indicator: The Sync History Log shows entries attempting to post to dates prior to the accounting lock date, with a Failed status. The GL shows movements in periods the finance team believed were protected.

Why Posting a Manual Journal Makes the Situation Worse

When the stock movement history returns nothing and the GL shows an unexplained movement, the natural response for a finance team is to post a manual corrective journal directly in Xero or QuickBooks Online to force the balances to agree. This feels like a pragmatic solution under month-end pressure.

It is a structural system hazard.

Here is what happens when a manual journal is posted to correct an inventory balance in the accounting platform without resolving the underlying cause in Cin7:

The root cause is masked, not resolved. The cost correction that caused the movement is still present in Cin7. On the next sync cycle, Cin7 pushes the system-generated adjustment journal again. The GL now contains both the manual journal and the re-pushed system journal for the same event. This creates a duplicate transaction listing that distorts the account balance in the opposite direction.
Sub-ledger integrity breaks. The balance in the Cin7 financial costing layer and the balance in the accounting platform GL are now permanently out of alignment. Every subsequent reconciliation must account for this manual override entry. Over time, as more manual journals accumulate to correct for the growing misalignment, the sub-ledger becomes effectively unreconcilable without a full transaction audit.
COGS is left in an incorrect state. The system-generated cost adjustment journals that caused the unexplained movement are Cin7 correcting its own FIFO/FEFO cost distribution to reflect actual invoiced costs. Reversing or overriding these entries with a manual journal means the reported COGS remains at the original estimated cost rather than the actual cost. Gross margin figures are incorrect. The distortion compounds across every subsequent period.

The correct response is to identify which of the five patterns is active and address the trigger in Cin7, not to suppress the symptom in the accounting platform.

What the Correct Operating State Looks Like

Passive inventory valuation shifts are not inevitable in Cin7 Core environments. They occur when specific operational timing gaps exist. Closing those gaps is the correct preventive approach.

Synchronized Period Locks Across Both Systems

The GRNI and GINR clearing accounts should be reviewed and cleared as part of every month-end close sequence, not left to accumulate across periods. An unresolved GRNI balance entering the next period means there is at least one invoice-to-receipt matching event that has not completed. That outstanding event remains a live exposure for Pattern 3 until the invoice is authorized and the clearing account reversal posts correctly.

Supplier Bills Matched Within the Same Accounting Month

The primary structural trigger for Patterns 1 and 2 is the timing gap between when goods are received and when the supplier invoice is authorized. When bills are received and matched within the same accounting month as the corresponding goods receipt, the FIFO/FEFO cost distribution uses the actual invoice cost from the outset. No retroactive correction is required because there is no retrospective variance to propagate.

In practice, this means purchasing teams need clear invoice receipt and authorization deadlines aligned with the accounting close calendar. The operational and financial calendars need to run in parallel.

GRNI/GINR Pipeline Cleared at Month-End

The period lock date in Cin7 Core must advance after every month-end close, in coordination with the lock set in Xero or QuickBooks Online. Locking only the accounting platform while leaving Cin7 open creates the Pattern 4 vulnerability. Locking only Cin7 while leaving the accounting platform open creates the reverse exposure.

For Xero and QuickBooks Online integrations, Cin7 is designed to sync period lock parameters between the platforms. If a backdated transaction predates the synchronized lock date, Cin7 marks the sync status as Failed to preserve ledger integrity. This only works if the lock is set correctly in the first place.

The correct month-end close sequence for this control to function:

Ensure all open sales invoices, purchase invoices, and physical dispatch fulfillments are fully authorized inside Cin7 before the close date.
Clear the entire integration sync queue until the failed transaction view shows zero outstanding items.
Extract the Inventory Movement Summary Report to verify physical stock valuation figures.
Cross-check balances against the GL asset accounts using the Financial Transactions vs Stock on Hand Difference Report to capture any outstanding accruals.
Post valid cut-off accruals, then execute period hard-locks across both Cin7 and the accounting platform simultaneously.

The Decision the Finance Team Actually Faces

Option B: Absorb the Variance in the Current Reporting Cycle

If the cost correction belongs in a prior period and that period is still accessible, the cleaner resolution is to temporarily unlock the period in both Cin7 and the accounting platform, allow the system-generated correction to sync and settle, and then re-lock the period.

This approach produces accurate period-specific financials. The COGS for the period in which the sale occurred reflects the actual cost of goods sold. The inventory asset value is correct for the balance sheet date. Comparative period analysis remains reliable.

The trade-off is that unlocking a prior period re-exposes it to change. If other backdated transactions are pending or additional invoices arrive late, the same exposure that created the original problem can recur during the unlock window. This approach requires careful queue management: clear the sync queue completely before unlocking, allow the specific correction to settle, and re-lock promptly.

This is typically the correct approach for Patterns 1, 2, and 3 when the period in question has not been filed externally or used in a compliance calculation.

Once the active pattern has been identified through the three-report diagnostic stack, the finance team faces a defined strategic choice. This is the decision that the standard troubleshooting content does not address, because standard content stops at pattern identification and does not engage with the operational trade-offs that follow.

Option A: Unlock the Prior Period and Let the Adjustment Settle

The choice between Option A and Option B cannot be made responsibly without knowing which pattern is active, what the materiality of the variance is, and what the compliance or filing status of the affected period is. Both options are legitimate. Neither is universally correct.

Making this call with a manual journal in the accounting platform is not a third option. It is a workaround that defers the actual decision while introducing the system integrity risks described in the previous section.

The Decision Requires Knowing the Pattern

If the prior period has been filed externally, used in a covenant calculation, or is otherwise no longer accessible without significant compliance risk, the alternative is to absorb the cumulative variance in the current active reporting cycle.

This means acknowledging the cost correction in the current period rather than the period it technically belongs to. The COGS figure for the prior period remains at the originally reported amount. A period-cost variance appears in the current period. Gross margin for the current period is affected by the correction rather than the original period.

This approach protects prior-period filings and avoids reopening closed books. It is the appropriate choice when the variance is within the 2% operational tolerance threshold and the period cannot be reopened without creating additional compliance exposure.

Patterns 4 and 5, governance failures and sync backlog processing, typically require the prior period to be examined and corrected regardless of which resolution path is chosen for the specific cost variance, because the underlying control failure needs to be addressed at source.

If the Trigger Is Still Unknown, the Diagnostic Is the Next Step

If your Cin7 inventory valuation has shifted without new transactions and the standard reports are not showing the cause, the trigger is likely sitting in the purchase ledger or the sync queue, not in the stock movement history where the investigation started.

The Fiskal Financial System Diagnostic looks across your Cin7 costing configuration, your integration sync logs, and your period lock governance to identify which of the five failure patterns is driving the movement. It examines both the Cin7 financial costing layer and the accounting platform GL simultaneously, because that is the scope the diagnosis requires.

If you are closing a period and the inventory numbers do not agree, and the stock movement history shows nothing, this is where the investigation should start.

What the Unexplained Movement Actually Is

Passive inventory valuation shifts in Cin7 Core are not random. They are not corruptions. They are the financial costing layer responding to events in the purchase ledger, events that occurred in a different system layer from where the visible movement appears.

The reason the standard audit trail shows nothing is structural: the physical stock movement layer and the financial costing layer operate independently. The trigger is in the purchase ledger. The audit trail for that trigger lives in the Financial Transactions vs Stock on Hand Difference Report, the Stock Received vs Invoice Report, and the Sync History Log.

Five patterns produce this outcome, each with a different origin and a different diagnostic path. The strategic decision, unlock the prior period or absorb in the current cycle, cannot be made responsibly without knowing which pattern is active.

What does not resolve any of them is a manual journal posted directly in the accounting platform. That suppresses the symptom, introduces duplicate sync records, and breaks the sub-ledger integrity that a clean reconciliation depends on.

The investigation starts by looking in the right layer.