What this is
What is a stock count variance investigation?
What is a stock count variance investigation?
It is the record of why a counted quantity did not match the system quantity, completed before the figure is changed. It captures the recount, checks against recent movements and open orders, the likely cause, and whether an adjustment is warranted, so count and adjustment are never conflated.
Who completes a stock count variance investigation?
The inventory controller, working from the count that raised the variance. It requires movement history and, usually, a conversation with whoever handled the location or item, so it cannot be done from the count sheet alone.
Is a variance investigation raised for every discrepancy?
No. It is raised when a variance exceeds the stated threshold. Discrepancies below that are ordinary count noise; the threshold reserves investigation for variances large enough to indicate a real process issue rather than rounding or timing.
Scope
When is a stock count variance investigation required?
This record is one step in a larger programme. Using it for work belonging to a neighbouring template produces records that are hard to report on later.
Use this template when
- A stock count has produced a variance above the stated investigation threshold
- A variance needs a documented cause before an adjustment can be authorised against it
- A pattern is suspected and needs checking against this and prior locations or items
- The variance needs linking forward to an adjustment or, where the cause is not simple, to a root cause analysis
- You are running the Inventory Accuracy programme and this is one of its steps
Do not use it for
- Recording the count itself, which belongs in the cycle count record that raised the variance
- Authorising the change to the system figure, which belongs in the inventory adjustment authorisation once the cause is understood
- Checking whether a location's contents match the system independent of a specific counted variance, which belongs in the stock location audit
- A deep structured investigation into a systemic or recurring cause, which belongs in root cause analysis once this record shows it is not a simple picking or receiving error
- A shortage identified through a route other than a scheduled count, such as a customer complaint, which belongs in the shortage investigation record
Compliance mapping
Which ISO 9001 cl.10.2 requirements does this satisfy?
No regulation names a stock count variance investigation directly. The obligation comes from quality systems requiring nonconformities to be evaluated before correction, and from the accounting reality that an unsupported adjustment is a control weakness, not just a shortcut.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 9001 cl.10.2.1 | React to nonconformity and evaluate the need for action to eliminate its cause, so it does not recur | Outcome |
| ISO 9001 cl.10.2.1 | Determine the cause of the nonconformity before deciding corrective action | Likely cause |
| ISO 9001 cl.7.1.5 | Ensure monitoring and measuring resources are suitable and results valid, relevant to confirming a counted figure | Checked |
| ISO 9001 cl.8.5.2 | Identification and traceability of product, relevant to confirming a variance is not a location error | Header |
| ISO 9001 cl.9.1 | Monitor, measure, analyse and evaluate process performance, relevant to detecting a pattern across locations | Evidence |
| ISO 9001 cl.7.5.3 | Documented information controlled and retained as evidence of conformity, relevant to sign-off and CAPA link | Outcome |
What it does not cover
- Cycle Count Record, which counts a defined slice of stock on a rolling basis and is the source of the variance, not its investigation.
- Inventory Adjustment Authorisation, which authorises and records the actual change to the system figure once the cause is understood.
- Stock Location Audit, which checks a location's holding matches the system, independent of any specific counted variance.
- Root Cause Analysis, the deeper investigation this record escalates to when the cause is not a straightforward picking, receiving or system error.
- Shortage Investigation Record, which investigates a shortage surfaced through a route other than a scheduled count, such as a customer complaint.
Global
Stock Count Variance Investigation requirements by country
No jurisdiction regulates a stock variance investigation by name. What differs is how strictly an unexplained adjustment is treated as a control weakness, in accounting terms as much as quality terms.
GAAP; Sarbanes-Oxley Act s.404 for public companies
Inventory adjustments must be supported by evidence for financial statement accuracy, with internal controls over the adjustment process.
An adjustment with no documented investigation behind it is an internal-controls deficiency an auditor tests for, not merely a shortcut.
Companies Act 2006 s.393; HMRC guidance on valuation of trading stock
Accounts must give a true and fair view, and reported stock values must be supportable.
A pattern of unexplained write-offs at the same location undermines confidence in the stock figure the accounts rely on.
ISO 9001:2015 cl.10.2
A nonconformity, here a stock variance, must be evaluated for cause before corrective action is decided, under a certified quality system.
A certification audit samples variance investigations to check whether the adjustment followed the analysis or preceded it.
How to complete it
How to complete a stock count variance investigation, step by step
The fields are straightforward. The judgement is whether the sequence they imply, recount, check, cause, then decide, was actually followed, or whether cause fields were filled in after the adjustment was already decided.
Recount Confirmed The Figure exists because a meaningful share of variances are counting errors, not stock errors. Investigating a cause for a discrepancy a recount would have dissolved wastes the exercise and risks a plausible-sounding explanation for something that never happened.
Variance, Variance Value and Variance Direction are arithmetic, produced automatically from the count. Likely Cause and Process Change Needed are judgement, never filled in to match a decision already made. Complete numbers with empty cause fields is a recorded discrepancy, not an investigated one.
Repeat Variance At This Location, On This Item and Pattern Across Locations only work if checked against actual history rather than memory. A location or item with a repeat history needs a process change, not another instance reaching the same open conclusion.
The record's structure puts Adjustment Recommended in Outcome, after Likely Cause and Evidence. An adjustment agreed informally before the investigation started, with the record completed afterward to support it, has inverted the sequence the form is built to enforce.
What auditors find
Most common stock count variance investigation findings
The record almost always exists once a variance crosses the threshold. The findings concern whether the sequence it implies was honoured, or the adjustment came first and the investigation followed to justify it.
| Finding | Clause | What fixes it |
|---|---|---|
| Adjustment ID recorded before Cause Identified or Process Change Needed were completed. | ISO 9001 cl.10.2.1 | Block or flag adjustment references entered ahead of a completed cause and process-change decision. |
| Recount Confirmed The Figure left blank or marked without an actual recount taking place. | ISO 9001 cl.7.1.5 | Require a recount before cause fields are enterable, and record who performed it. |
| Repeat Variance At This Location and On This Item both marked no without checking history. | ISO 9001 cl.9.1 | Cross-check both fields against prior investigations for the same location and item before answering. |
| Likely cause checklist (picking, receiving, putaway, damage, system, theft) marked N/A across the board. | ISO 9001 cl.10.2.1 | Require each likely-cause field to be genuinely assessed against movement history, not defaulted N/A. |
| Camera footage or movement history marked reviewed with no record of what was found. | ISO 9001 cl.9.1 | Capture what the movement history or footage showed, not just that it was checked. |
| Action Required marked yes with no CAPA ID or action owner recorded. | ISO 9001 cl.7.5.3 | Require an owner and reference when an action is raised, not left for a later update that may not happen. |
Case in point
Case in point: the investigation that existed but was never performed
A packaging supplier ran a monthly cycle count across its label and film stock. One location, a small run of a particular label, came up short just above threshold. The inventory controller recounted, confirmed the shortfall, and opened an investigation. Every likely-cause field, picking error, receiving error, wrong putaway, damage, system error, theft, was marked not applicable. Adjustment Recommended was marked yes, an adjustment authorised the same afternoon, and the investigation signed off.
The following quarter, the same location produced the same variance on the same label, again just above threshold. Repeat Variance At This Location, this time, was answered honestly as yes, and a look back showed the first investigation had never reviewed the movement history it claimed to have checked. The likely causes had been marked not applicable because nobody had looked, not because they were ruled out. The record existed in full, every field populated, and had investigated nothing.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
5 sections
- Reference
- LOG-014
- Archetype
- Record
- Record ID
- SCV-2026-000
- Scoring
- Variance explained
- Direction
- High is good
- Singleton
- No
- Basis
- ISO 9001 cl.10.2
- Links
- Feeds Inventory Adjustment and RCA
- Tags
- Inventory, Variance
- Sections
- 5
- Fields
- 48
- Follow up fields
- 3
- Repeating sections
- 0
- Links out
- 6
Header
16 fieldsInvestigation ID*
Auto sequence. Format SCV-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Count ID
Links to LOG-013 Count ID
Material
Location Reference*
System Quantity*
Counted Quantity*
Variance*
Variance Value
Variance Direction*
Stock gain or stock loss.
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Above Investigation Threshold*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Adjust Without Investigating And It Repeats
A variance written off at month end is a process failure converted into an accounting entry. The same location will produce the same variance next quarter.
Checked
6 fieldsRecount Confirmed The Figure*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Adjacent Locations Searched*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Unit Of Measure Verified*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Recent Movements Reviewed*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Open Orders And In Transit Checked*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Batch Split Considered*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Likely cause
6 fieldsPicking Error*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Receiving Error*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Putaway To The Wrong Location*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Unrecorded Damage Or Scrap*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
System Or Interface Error*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Theft Considered*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Evidence
6 fieldsMovement History Reviewed*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Camera Footage Reviewed Where Available*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
People Involved Spoken To*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Repeat Variance At This Location*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Repeat Variance On This Item*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Pattern Across Locations*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Outcome
14 fieldsCause Identified*
Cause Detail
Process Change Needed*
- No3 pts
- Yes1 pt
Adjustment Recommended*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Adjustment ID
Links to LOG-015 Adjustment ID
RCA ID
Links to FDN-013 RCA ID
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Inventory Controller*
Signature*
Warehouse Manager*
Second Signature*
LOG-014 · record IDs look like SCV-2026-000 · Feeds Inventory Adjustment and RCA
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The record is a document. What fails is the discipline around it: the recount skipped to save time, likely-cause fields ticked not applicable because nobody looked, and the adjustment posted before the investigation meant to justify it.
Links each variance investigation back to the cycle count that raised it and forward to the adjustment it authorises, so the sequence cannot be skipped.
Watches for investigations with likely-cause fields marked not applicable across the board, and routes recurring variances toward root cause analysis.
Rolls repeat-variance flags across locations and items into a single view, surfacing patterns a single investigation would not show.
Holds every adjustment for approval until the linked investigation shows a completed cause and process-change decision, not just a populated form.
This template lives in KnowLogistics — supply chain execution. Inbound, outbound, inventory, yard, claims, supplier lifecycle and customs.
Glossary
Stock Count Variance Investigation definitions and key terms
- Variance
- The difference between the counted quantity and the system quantity for a location and item, before any judgement is made about why it exists.
- Variance direction
- Whether the variance is a stock gain or a stock loss, which shapes which likely causes are worth checking first.
- Investigation threshold
- The size of variance above which an investigation is required, set so ordinary count noise does not trigger one every time.
- Likely cause
- The set of plausible explanations checked against movement history: picking error, receiving error, wrong putaway, damage, system error or theft.
- Adjustment
- The change made to the system quantity once the cause is established, authorised through a separate record rather than decided within this one.
FAQ
Frequently asked questions about stock count variance investigation
Should a variance be adjusted before or after the investigation?+
After. Adjusting first and investigating afterward, even briefly, produces a record that exists to justify a decision already made rather than inform one. The form's structure, cause and evidence sections ahead of the adjustment recommendation, reflects that the investigation comes first.
What should happen first when a variance is raised?+
A recount. A meaningful share of variances above threshold turn out to be counting errors, not stock errors, and investigating a cause for a discrepancy a recount would have dissolved wastes the exercise.
What does above investigation threshold actually mean?+
That the variance is large enough to warrant a full investigation rather than being treated as ordinary count noise or timing difference. The threshold reserves investigation for variances likely to indicate a genuine process issue.
Why does the record ask about repeat variance separately from likely cause?+
Because a single cause field cannot tell a one-off mistake from a systemic problem. Repeat Variance At This Location, On This Item and Pattern Across Locations exist to catch the case where the same explanation keeps recurring, changing the response from a correction to a process fix.
When should this escalate to a root cause analysis instead?+
When the cause is not a simple, single-instance error, but tied to a process, training gap or recurring pattern. This record establishes that escalation is needed; it is not the vehicle for the deeper analysis itself.
Who needs to sign off the investigation?+
The inventory controller who ran it, and the warehouse manager as second signature. Two signatures exist because an investigation only its author approves has no independent check on whether cause fields were genuinely assessed.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Inventory Accuracy
Storage Location Register
Holds every rack, bay, chamber and yard position where material is stored, with its capacity and conditions
Cycle Count Record
Counts a defined slice of stock while operations continue, rather than shutting the site once a year
Inventory Adjustment Authorisation
Authorises a change to a system stock figure, with the reason and the evidence behind it
Stock Location Audit
Checks that what the system says is in a location is actually in that location, and nothing else is
Damaged Stock Record
Records stock damaged in storage or handling, how it happened and what was done with it
Expiry and Rotation Check
Checks that stock is being rotated correctly and that nothing is approaching or past its date
More in Inventory
Cycle Count Record
Counts a defined slice of stock while operations continue, rather than shutting the site once a year
Inventory Adjustment Authorisation
Authorises a change to a system stock figure, with the reason and the evidence behind it
Stock Location Audit
Checks that what the system says is in a location is actually in that location, and nothing else is
Damaged Stock Record
Records stock damaged in storage or handling, how it happened and what was done with it
Expiry and Rotation Check
Checks that stock is being rotated correctly and that nothing is approaching or past its date
Consignment Stock Reconciliation
Reconciles stock held on site but owned by somebody else, or held elsewhere but owned by you
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 9001:2015 clauses 10.2, 8.5.2, 7.1.5, 9.1 and 7.5.3
- Sarbanes-Oxley Act Section 404, internal controls over financial reporting (US)
- Companies Act 2006, section 393, true and fair view of accounts (UK)
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.