We use cookies to understand which pages and tools are useful, nothing more — no ad tracking across other sites. You can change this later from the footer.

Skip to content
Lekhya.in

Guide6 min readPublished

Investigating inventory shrinkage and count variances

How to tell genuine inventory shrinkage from theft, evaporation or breakage apart from a counting or data error, what materiality threshold justifies investigating a variance, and who should authorize the resulting write-off.

Investigating inventory shrinkage means working out whether a difference between book and physical quantities is a genuine loss of goods — theft, evaporation, breakage, or process yield loss — or an error in the counting or the underlying data, before accepting management's proposed write-off. Investigation should be triggered by value-based thresholds rather than quantity, and the resulting write-off needs a specific authorization trail, not a single blanket journal entry passed at year end.

Genuine shrinkage versus an error masquerading as shrinkage

A count-to-book variance has exactly one of two underlying causes: stock that genuinely no longer exists in the quantity the books assume, or a record somewhere that is simply wrong. These need entirely different responses, and the investigation has to establish which one it is before any write-off is proposed.

Causes that produce an identical-looking variance on the count sheet
CauseCategoryHow to tell it apart
Theft or pilferageGenuine lossPattern across specific high-value, easily resold SKUs, or at a specific location or shift; consider the control environment around that stock
Evaporation, moisture loss, process yield lossGenuine lossIndustry-typical rate for that material and process; a documented, expected loss factor the client should already track
Breakage and damageGenuine lossShould be supported by a damage report or scrap record created at the time, not invented after the variance is found
Unit-of-measure mismatch between the count sheet and the book recordData/counting errorRecompute the count in the book's unit of measure before comparing; a frequent and easily resolved false variance
Unrecorded transaction (a GRN or dispatch posted late, or not at all)Data/counting errorTrace the item's transaction history around the count date for a posting gap
Miscount on the dayData/counting errorRecount the specific item if the audit is still on site; otherwise assess plausibility against the quantities and layout involved
Duplicate or omitted count sheet for a sub-locationData/counting errorConfirm every count sheet for every location/bin was captured once, and only once, in the consolidated file
Causes that produce an identical-looking variance on the count sheet

The investigation sequence

  1. 01Rule out data errors firstUnit of measure, posting cut-off, and duplicate or missing count sheets are the cheapest explanations to check and the most common cause of a variance that looks alarming but is not real. Clear these before assuming the loss is genuine.
  2. 02Check the transaction history for the specific item around the count dateA gap in recorded movement right before or after the count date often explains an apparent shortage without any stock actually being missing.
  3. 03Ask for the client's own explanation, in writing, item by itemNot a blanket explanation for the total variance. A specific explanation per significant item, or per category of similar items, that can be corroborated.
  4. 04Corroborate the explanation against an independent sourceA damage report created at the time of the damage, not reconstructed afterward; a security incident log for a theft claim; an industry-typical yield-loss percentage for an evaporation or process-loss claim.
  5. 05Look for a pattern across periodsA shrinkage rate rising steadily year over year at a specific location, with no corresponding change in process or product, is a different conversation from a one-off variance — it points toward a control weakness that needs addressing, not just an accounting entry.

A variance quietly absorbed into a 'stock adjustment' ledger account with no breakdown by item or cause, year after year, is a sign that shrinkage is being written off as a matter of routine rather than investigated. The account balance itself, over several years, is worth trending.

Setting a materiality threshold for investigation

Investigating every single-unit variance across a large stock-keeping unit count is not a sensible use of time, and no audit does it. The threshold needs to be set deliberately, by value, and applied consistently rather than chosen to avoid uncomfortable items.

  • Set a value threshold, not a quantity or percentage threshold alone — a thousand-unit variance on a low-value fastener and a five-unit variance on a finished product can carry the same rupee exposure.
  • Lower the threshold, or investigate regardless of value, for items that are easily resold, cash-equivalent, or previously flagged as a control concern.
  • Aggregate small variances across similar items before dismissing them individually — a pattern of small negative variances across an entire product line sums to something material even if no single line crosses the threshold.
  • Document the threshold chosen and the basis for it in the working paper, so a reviewer can assess whether it was set appropriately rather than reverse-engineered from the results.

Write-off authorization

Once a variance is accepted as genuine shrinkage rather than a data error, the write-off itself needs a documented approval trail appropriate to its size — this is a control test as much as a substantive one.

  1. 01Confirm the client has a stated approval limit for inventory write-offsWho can approve what value, and whether larger write-offs escalate to a more senior authority or the board — many mid-market clients have no written policy at all, which is itself worth noting.
  2. 02Trace the write-off journal to its approvalA signed or system-logged approval at the appropriate level, dated before or at the time of the write-off, not backdated afterward to support an entry already passed.
  3. 03Check for split write-offs designed to stay under an approval thresholdSeveral write-offs for the same cause and around the same date, each individually below the approval limit, is a pattern worth asking about directly.
  4. 04Confirm the write-off is reflected consistently in both the financial books and the stock/quantity recordsA write-off passed only in value, with the quantity still showing in the perpetual stock system, leaves a reconciling item that will resurface at the next count.

Regulatory requirement

Where inventory shrinkage is material, it affects the measurement of inventory under AS 2/Ind AS 2 and may also be relevant to the auditor's reporting under the Companies (Auditor's Report) Order, which specifically asks whether discrepancies noticed on physical verification were properly dealt with in the books of account.

How we think about this

Clearing unit-of-measure mismatches, tracing transaction gaps around a count date, and matching write-off entries to their approvals are rule-based checks that should run across every variance in the count, not a sample selected because the full list is long. Deciding whether a specific explanation for a genuine loss is credible, and what a rising shrinkage trend actually says about the control environment, is the part that stays with the auditor.

This is practical guidance written for audit teams, not an authoritative statement of any standard or statute. Standards, forms and timelines change. Check the current text issued by the ICAI and the relevant authority before relying on anything here in an audit file.

Free tools, no signup

Each one reads a file entirely in your browser — or, for two of them, just answers a few questions — and nothing is ever uploaded.