Why Your Inventory Doesn’t Match Your Books in Cin7

Inventory discrepancies aren’t always a counting problem

SYSTEMS AND SOFTWAREECOMMERCE

Pierre Goldie

4/10/20263 min read

Why Your Inventory Doesn’t Match Your Books in Cin7

Pierre Goldie, Co-founder & CGO @ Fiskal

Inventory discrepancies aren’t always a counting problem

If your inventory doesn’t match your financials, the default response is operational:

  • Run another stock take

  • Adjust quantities

  • Clean up transactions

Sometimes that helps.

But in many Cin7 environments, discrepancies persist even when stock counts are correct.

When that happens, the issue isn’t the count.

It’s how inventory flows through your system.

TL;DR

  • Inventory can match physically but still be wrong financially

  • Stock takes reconcile quantity, not necessarily value

  • Timing, cost allocation, and integrations influence valuation

  • Manual fixes often address symptoms, not causes

  • Resolving this requires system-level diagnosis

When quantity matches, but value does not

Can inventory be correct but still not match the books?

Yes.

Because inventory quantity and inventory value are not automatically aligned.

A stock take verifies physical stock. Financials reflect how that stock is recorded across systems.


The key guardrail: quantity does not equal value

Stock takes reconcile quantity.

They do not automatically reconcile value.

If adjustments are made without assigning cost:

  • Quantity may be correct

  • Inventory value may remain unchanged


The financial reality

Inventory = Opening Balance + Purchases - Cost of Goods Sold

This relationship must hold.

But it depends on how transactions are recorded across systems, not just how stock is counted.


Why discrepancies appear after go-live

Most Cin7 environments don’t fail at setup. They drift.

Over time, small inconsistencies accumulate:

  • Transaction timing differences

  • Incomplete workflows

  • Integration dependencies

These are not usually software defects.

They reflect misalignment between workflows, configuration, and accounting logic.


How inventory actually flows through your system

Inventory and financial postings are driven by transaction events, which may occur at different stages depending on configuration, workflow, and integration setup.


Sales

  • Revenue may be recorded at invoicing

  • Inventory may be reduced at shipment


Purchasing

  • Liability may be recorded at invoice

  • Inventory updated at receipt


Why this matters

These events do not always happen at the same time.

Transactions can be correct individually, but misaligned collectively.


The failure patterns behind discrepancies

These patterns are commonly observed in live Cin7 environments.


Adjustment without cost

Adjustments change quantity.

They only affect valuation if cost is included.

Result:

  • Quantity is corrected

  • Value remains unchanged


The GINR effect

When goods are invoiced but not fully received:

  • Value sits in a clearing account

  • Inventory appears understated

Guardrail: Do not clear GINR manually in accounting systems. This can lead to double-counting when Cin7 posts later entries.


Backorder and integration behaviour

In certain configurations:

  • Transaction status can change how data is exported

  • Mapping behaviour may differ between systems

Guardrail: This depends on configuration and integration setup. It is not a fixed rule.


Timing mismatches

Invoicing, shipment, and receipt occur at different stages.

This means:

  • Postings may not align

  • Discrepancies can emerge


Unit of measure misalignment

If purchasing and selling units differ without proper conversion:

  • Cost calculations can become inconsistent

  • Valuation can become unreliable


Cost allocation gaps

If costs such as freight or duties are not allocated to inventory:

  • Inventory may be understated

  • Margins may appear inflated


Where discrepancies usually originate

Not in the count.

They typically originate at system interaction points:

  • Transaction timing

  • Incomplete workflows

  • Integration dependencies

  • Cost allocation

You cannot fix a discrepancy without identifying its origin.


Why standard fixes often fail

Stock takes and adjustments focus on quantity.

They do not resolve system-level alignment.

As a result:

  • Discrepancies may be corrected temporarily

  • Then return


Why this matters

Inventory discrepancies affect:

  • Cost of goods sold (COGS)

  • Margins

  • Reporting reliability

  • Audit readiness

If inventory is wrong, financial decisions become unreliable.


How to recognise a system-level issue

  • Discrepancies persist after stock takes

  • Repeated adjustments are needed

  • Reports don’t reconcile

  • Clearing accounts grow

Recurring issues usually indicate structural misalignment.


What aligned systems look like

When workflows, integrations, and accounting logic are aligned:

  • Inventory reconciles

  • Cost flows consistently

  • Reporting becomes reliable

This is not driven by effort. It is driven by alignment.


The Fiskal perspective

Across Cin7 environments, the issue is rarely how transactions are recorded individually.

It is how systems behave together.

Fixing discrepancies requires:

  • Understanding system interactions

  • Identifying where value diverges

  • Correcting alignment across systems

A Stable Month-End Close Is a System Outcome

If your inventory doesn’t match your books, the issue isn’t your stock take.

It’s how your system handles inventory across purchasing, sales, and accounting.

Diagnostic next step

If your inventory does not reconcile to your financials, the issue may not be the count. It may be how your system is configured and operating.

A structured Inventory & Finance Alignment Review helps identify where discrepancies originate and restore accurate, reliable reporting across your systems.

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

Share on your socials.