Count Variances

Verify inventory quantities in the system actually exist on the shelf.

  • Ledger + 2 client documents
  • Key analysis in Inventory

How the result is read

Negative variance with no JE is unrecorded shrinkage; positive variance with no receipt is a phantom receipt. Counts are almost never taken on the balance-sheet date, so movements are rolled to a common date before any variance is struck. Coverage is always reported, and coverage is not projection.

The worksheet, on the demo engagement

Count Variances, as the application draws it for Harrow Precision Engineering Ltd, the fictional demo engagement — one row per SKU per location counted.

Counted against the system, item by item
0780k1.6MSystem quantityCounted quantity

On the diagonal the count agrees; flagged items are marked.

Items counted
842
Count variances
14
Gross negative variance
(658)
Unadjusted — the misstatement
(631)

Physical count reconciliation (IAS 2.36), with movements between the count date and period end rolled forward so both sides are as at the same moment. Positive and negative variances are reported gross rather than netted — an overstatement in one bay and an understatement in another are two errors: gross negative (658), gross positive +27. Only Bay 9 carries a correcting entry, so the misstatement is the (631) left unadjusted, not the (1,207) net of everything. Values in thousands. Feeds M-06 alongside NRV and SLOB.

Result grid5 rows
SKULocationSystem qtyCount qtyVarianceUnit cost
FG-1201Warehouse A — Bay 4400,000372,000(28,000)12.50
FG-1210Warehouse A — Bay 9200,000168,000(32,000)18.00
HW-4310Warehouse B — Bay 24,0004,000053.75
RM-0099Raw store — Shelf 31,500,0001,560,000+60,0000.45
FG-1220Warehouse A — Bay 1300,000286,000(14,000)22.00

In the application

Count Variances is filed under Inventory, index letter E. "Run all analyses" runs it with every other analysis the ledger and the documents loaded can answer. The worksheet states the population it tested on its face — or "Not applicable" with the reason when a column it depends on is empty — and the Excel workbook the engagement exports files it under E, beside an index of the source files with their SHA-256 fingerprints.

Run your next audit file test without the Excel crash.

One free engagement to evaluate, valid 60 days. The ledger never leaves the machine.

  • 20 minutes
  • Runs on a fictional engagement
  • No client data required

Cookie settings

This site sets no cookies. It keeps one preference in your browser's localStorage — the currency you chose on the pricing pages — and its analytics are cookieless, so there is nothing to opt in or out of.

View Cookie Policy