Why Cin7 Manufactured Margins Are Wrong

A correct Cin7 BOM can still produce a wrong manufactured margin. See where cost timing breaks and how to trace the gap before it hits your P&L.

SYSTEMS AND SOFTWARE

Juandre Nortier

8/24/20269 min read

Signs Your Cin7 Implementation Needs an Independent Review

Juandre Nortier, ERP Systems Lead @ Fiskal

A Cin7 implementation rarely fails all at once. It shows up first as a small variance that will not close.

That variance is not automatic proof the implementation failed. It is also not necessarily a reflection of your team's competence. Most businesses one to six months past go live see some level of mismatch between what Cin7 says and what the general ledger says. If you have not run a broader Cin7 implementation health check yet, this article picks up specifically where that mindset question leaves off, with the one number worth checking first.

The question worth answering is not whether a mismatch exists. It is whether that mismatch is still settling in, or whether it has crossed into something structural.

Most businesses in this position are weighing the same three decisions at once. Whether to request another round of fixes from the original implementation partner. Whether to bring in an outside reviewer now, or wait for a clearer failure point to appear. Whether the current variance is still inside a normal post go live window, or has already crossed into structural territory. None of these decisions is obvious from inside the business, because the uncertainty itself is part of the problem. It is not always clear whether the issue reflects the internal team's inexperience or a flaw in how the system was originally built, and asking for outside review can feel like it risks the relationship with the partner who built the setup in the first place.

The clearest sign a Cin7 implementation needs independent review is not a support ticket. It is a reconciliation variance that will not close. Left unresolved, that variance compounds through manual journal workarounds and increasingly distorts margin, cost of goods sold, and cash flow. Going back to the original implementation partner for another point fix is one option, not the only one. An independent review is a separate, non adversarial path.

TL;DR

A persistent variance, commonly above 2 percent in Fiskal's client work, between Cin7 stock valuation and the GL Inventory Asset account, measured on a closed month end reconciliation report rather than a live dashboard figure, is the clearest signal an implementation needs independent review, not a support ticket count.
In Fiskal's experience, settling in issues typically resolve within 30 to 60 days or the first peak trading season. Issues still present past that window may point to a structural configuration flaw.
Manual journal entries used to force balance sheet alignment bypass the Cin7 item sub ledger and can make the underlying gap harder to trace over time.
Repeated point fixes from the original implementation partner will not resolve a shared root cause if that cause was never diagnosed.
Independent review is a distinct, non adversarial option, separate from waiting it out or escalating to a full rescue.

How Do I Know If My Cin7 Implementation Needs An Independent Review?

A Cin7 implementation typically needs independent review when three conditions line up together, not just one.

First, a variance commonly above 2 percent in Fiskal's client work between Cin7 stock valuation and the GL Inventory Asset account, confirmed on a closed month end reconciliation report rather than a live dashboard figure, and still present past the 30 to 60 day settling in window Fiskal typically observes. Second, sync errors that keep accumulating rather than clearing on the Cin7 integration screen. Third, an internal team that cannot explain why the current configuration behaves the way it does when asked directly.

Any one of these on its own may not mean much. Together, they often point to a setup that was never fully closed out.

Why does my Cin7 inventory not match my Xero or QuickBooks balance?

The variance often traces to account mapping, timing gaps between supplier invoices and stock receipts sitting in Goods Received Not Invoiced (GRNI) or Goods Invoiced Not Received (GINR) clearing accounts until resolved, or unclosed historical orders older than three months.

Manual journals posted to correct the balance sheet commonly bypass the Cin7 item sub ledger, which can widen the gap rather than close it. Lock date misalignment between Cin7 and the accounting system is a separate, specific failure mode worth checking on its own.

Should I Ask My Implementation Partner for Another Fix, Or Bring In An Independent Reviewer?

Another point fix will not resolve a shared root cause if that root cause has never been diagnosed. Independent review is a diagnostic step, not a replacement for the existing partner relationship.

Waiting past the 30 to 60 day settling in window Fiskal typically observes, without progress, raises the risk of the issue becoming a full rescue situation instead of a contained one.

What Most Cin7 Content Gets Wrong

Most published guidance on post go live issues treats them as generic software complaints or a general diagnostic checklist. It does not connect the signs to what is happening on the financial statements.

This article treats the review as an objective, forensic comparison of the sub ledger and the standard operating procedures behind it. It is not a pitch to replace the existing implementation partner.

The Manual Journal Bypass Loop

Most unresolved variances follow the same sequence, whether or not the business can see it happening.

Initial setup establishes core workflows and account mappings, including Inventory Asset, cost of goods sold, and Goods Received Not Invoiced. Real world operational volume then introduces complications that were not visible during testing, such as partial fulfillments, price differences between a purchase order and its invoice, or unlinked ecommerce fees. At that point, staff often patch the balance sheet gap with a manual journal in Xero or QuickBooks, rather than correcting the source transaction inside Cin7.

This is where the loop closes, and why it tends to repeat.

Cin7 Core calculates cost of goods sold dynamically, at the time of sale fulfillment or invoice authorization, based on each SKU's costing method, whether that is FIFO, FEFO, or Special Batch. A manual journal entered directly in Xero or QuickBooks exists only in the general ledger. The Cin7 item sub ledger and its underlying SKU cost layers remain unchanged.

Because the sub ledger is never corrected, every subsequent sale generates a new automated cost of goods sold journal from Cin7, calculated from the same unadjusted unit costs. The general ledger and the sub ledger diverge further with every sales cycle, rather than converging.

This matters for two reasons. It shows the variance is not random. It is the predictable output of a specific, traceable sequence. And it explains why repeated manual fixes do not resolve the issue, and can make it harder to trace later, since each fix treats the symptom on the balance sheet while leaving the sub ledger untouched.

Is My Cin7 Implementation Set Up Correctly?

Run this as a self check rather than a general impression.

The problem worth investigating is a persistent variance between Cin7 stock valuation and the GL Inventory Asset account. A single mismatched number on one report is not the same thing, and does not need the same response.

That variance shows up inside the accounting platform, Xero or QuickBooks, not inside Cin7 itself. This is one reason the two systems get searched together when something feels wrong. In Fiskal's client work, a variance commonly above 2 percent is worth checking on a closed month end reconciliation report: compare the Cin7 Inventory Movement Summary to the GL Inventory Asset account as of a specific historical date. A live or mid day dashboard number will often show a variance that a closed reconciliation would not confirm, because of pending ecommerce sync queues, unposted fulfillment logs, and unposted daily consolidation invoices.

Where the Variance Usually Comes From

A persistent variance is rarely one cause. It is usually one of three, and sometimes more than one at once.

This list reflects the most common causes Fiskal sees. It is not exhaustive for every business.

What Happens Inside the System

This is the Manual Journal Bypass Loop from above, playing out in the reports the reader is looking at. Initial setup establishes mappings. Real world volume introduces complications. Staff patch the balance sheet instead of correcting the source transaction in Cin7. The sub ledger stays wrong, so cost of goods sold keeps posting against the same incorrect baseline every cycle.

The downstream effect reaches further than the balance sheet. An unreliable gross profit percentage and distorted cost of goods sold are the most visible impact. Misstated Inventory Asset values follow closely behind. Stale balances sitting in GRNI or GINR from unclosed orders can also corrupt 13 week cash flow projections and MRP reorder triggers, since both depend on inventory figures that are no longer accurate.

None of this shows up as a single dramatic failure. It shows up as a slow erosion of trust in the numbers themselves. A gross profit percentage that looks lower than it should, without an obvious cause. A cash position that seems tighter than the sales figures suggest it ought to be. A reorder recommendation that does not match what is actually sitting in the warehouse. Each of these can be explained away individually. Together, they usually trace back to the same unresolved sub ledger gap.

Cin7 Audit Checklist

Use this as a checklist you can run yourself, not as a single test that proves anything on its own. No pattern here is proof by itself. Weigh them together.

Lock Date Misalignment is worth calling out on its own. It is a distinct integration error, not a generic sync failure, and it happens specifically at the boundary between an operational edit in Cin7 and an accounting period that has already been closed.

What You May Be Telling Yourself

Three beliefs tend to keep businesses stuck longer than necessary.

The first is that recurring variances are teething issues that will resolve as staff get more comfortable with the system. Sometimes true, and worth ruling out with proper staff training versus structural configuration review first. In Fiskal's experience, not reliably true past the 30 to 60 day window.

The second is that going back to the original implementation partner for another fix is the only available option. It is one option. It is not the only one. Asking a different party to look at the setup is not an accusation against the team that built it. It is a routine check on a system that now carries real financial weight.

The third is that manual journal entries are a reasonable way to keep the books looking right in the meantime. They keep the balance sheet looking right. They do not correct the sub ledger, which is where the underlying number actually lives. The books can look correct at a glance while the system generating those numbers continues to drift further from reality underneath.

What a Correctly Closed Out Implementation Looks Like

Putting It Together

Three beliefs tend to keep businesses stuck longer than necessary.An unresolved variance compounds into unreliable margin and inventory reporting, and a growing risk of cash flow and reorder distortion. It does not resolve itself with time.

Independent review is the mechanism that distinguishes settling in from a structural flaw, using a specific threshold and window rather than a guess. Requesting a review is not the same as replacing the existing implementation partner. It is a diagnostic step that either confirms the setup is sound or defines exactly what needs to be corrected, and protecting the investment you already made in the platform rather than absorbing the cost of a system that quietly drifts further out of alignment.

Every part of this diagnostic traces back to the same starting point. A reconciliation variance that will not close is a system telling you something specific, not a system telling you something is generally wrong. The Manual Journal Bypass Loop shows why the gap compounds. The root cause table shows where it usually starts. The checklist shows how to confirm it without guessing. None of these require the reader to take anyone's word for it. Each one can be checked directly against the reader's own reports.

When a Variance Points to Something Structural

A recurring reconciliation variance after go live usually points to an unresolved configuration or workflow gap, not a people problem that will resolve on its own.

If the signs in this article sound familiar, an independent review can confirm whether the variance traces back to mapping, timing, or an unclosed order, and what it would take to close the gap. Fiskal's independent Cin7 implementation review looks at sub ledger parity and workflow standard operating procedures directly, without assuming the original implementation was at fault.

The Signal Worth Trusting

The signal worth trusting is the reconciliation variance itself, not a support ticket count or a general feeling that something is off.

Settling in and structural flaws are distinguishable using a specific window and a specific threshold, not guesswork. Independent review is a distinct, non adversarial path forward, separate from waiting it out and separate from a full rescue engagement.

The problem is not that your team is still learning the system. The system itself may never have been fully closed out.