Inventory Variance: How to Investigate and Reconcile Stock Count Differences

Quick answer: investigate before adjusting

Inventory variance is the difference between a physical quantity and a recorded quantity for the same item, unit, location scope, stock status, and reference time. Start with a controlled recount. Confirm the unit of measure and SKU, search other storage areas, and review receipts, sales, usage, returns, and write-offs around the count cutoff. Only then decide whether a correction is justified.

A discrepancy establishes a mismatch. It does not establish theft, employee fraud, supplier fraud, or a particular shrinkage cause. Keep the original count and system snapshot as evidence. If a second count or missing document explains the difference, correct that specific error. If evidence remains incomplete, record an unresolved discrepancy and assign an owner rather than inventing a reason.

What inventory variance means

A stock count discrepancy can arise from physical stock, the records, or the comparison itself. Counting only a front shelf against a quantity that includes the back room creates a scope mismatch. Comparing sellable stock against a balance that includes quarantined goods creates a status mismatch. Comparing an afternoon count with yesterday’s export creates a time mismatch.

Write down the comparison boundary before investigating: item identifier, variant, counted unit, included areas, treatment of damaged and reserved goods, and cutoff time. Do not confuse physical on-hand quantity with available-to-sell quantity. A reserved unit may still be physically present. An owned damaged unit may be present but unusable. The correct treatment depends on the business’s stock definitions.

The variance formula and its limits

Signed quantity variance = physical quantity − recorded quantity. With a recorded quantity of 24 and a physical count of 19, the variance is 19 − 24 = −5 units. The minus sign means fewer units were counted than recorded. Use this sign convention consistently in exports and investigation notes; some systems display the opposite convention.

If a percentage helps prioritize review, define it explicitly: signed variance percentage = (physical quantity − recorded quantity) ÷ recorded quantity × 100. The example is approximately −20.83%. When the recorded quantity is zero, this percentage is undefined; report the unit difference instead. This is a discrepancy measure, not an inventory accuracy score or proof of a loss.

Calculate a value difference only with a stated, consistent valuation basis. Quantity multiplied by an agreed unit cost can help prioritize attention, but it is not an accounting journal entry. Do not mix selling prices for one item with costs for another. This guide addresses operational quantities, not tax treatment or financial-statement reconciliation.

Inventory Accuracy Formula: How to Measure Stock Accuracy After a Physical Count

Positive and negative variance need investigation

A negative variance means the physical quantity is below the recorded quantity under the chosen convention. Possible explanations include a missed bin, an unrecorded issue, a duplicated receipt, or genuine loss. A positive variance means more stock was counted than recorded. Possible explanations include an unposted receipt, a missed customer return, duplicate counting, or a wrong item assignment.

Neither direction is automatically good or bad. Extra units assigned to the wrong SKU can hide a shortage in the correct SKU. A negative figure can disappear after an independent recount. Examine both signs with the same discipline and avoid rewarding a count merely because it increased the recorded balance.

Why netting discrepancies is dangerous

Suppose one SKU has a shortage of 5 units and another has an excess of 5 units. A net total of zero hides two unresolved item records. The products may have different costs, uses, or reorder needs. One discrepancy may be an identity error while the other is a timing error; equal quantities do not prove they share a cause.

Keep positive and negative discrepancies visible by item and, where relevant, location and stock status. Investigate a suspected swap together, but close each affected record with evidence. Summaries can show the net difference alongside gross shortages and gross excesses. Never let the net figure replace the underlying lines or suggest that all inventory records are accurate.

Step 1 — recount the SKU

Pause movement in the affected area where practical, or log every movement during the recount. Ask a second person to count independently without being told the expected total. If you work alone, restart from the opposite end of the shelf and record subtotals by area. Count actual contents of open cartons rather than multiplying a printed carton quantity.

Keep the first count, second count, counter, time, and included areas. A blank count is not zero. Mark empty locations explicitly and distinguish an inaccessible area from an area checked and empty. If counts disagree, resolve the difference physically before editing the stock record. Use the physical-count guide for a broader preparation checklist.

Step 2 — confirm the unit of measure

Check whether the system quantity means individual pieces, packs, cases, kilograms, litres, or another base unit. A carton and an individual item can be the same product at different packaging levels. Record full sealed cartons separately from loose units, verify the actual pack size, and convert both to the agreed stock unit before comparing totals.

Do not assume every carton contains the same quantity. Mixed cartons, broken packs, and a changed supplier pack size deserve a physical check. For measured consumables, use the business’s consistent measurement method and record any estimate. Do not silently convert a rough estimate into an exact count. Correct a bad conversion rule only after checking its other affected records.

Sources: SAP Learning — Conducting Inventory Counting and Inventory Posting; GS1 — GTIN Management Standard

Step 3 — check barcode and SKU identity

Read the product description, size, flavour, colour, and pack level as well as the scanned code. Confirm that the code resolves to the intended internal SKU. Search for duplicate barcode mappings and duplicate product records. A successful scan proves that a code was read; it does not prove that the local mapping or selected variant is correct.

Look at neighbouring items with similar packaging. If one appears short and another appears over, recount both before deciding that units were swapped. A barcode printed on a shipping carton may identify a different trade item from the barcode on an individual unit. Retain the original identifiers in your investigation note so a later mapping correction does not erase the trail.

Sources: GS1 — GTIN Management Standard

Step 4 — check another shelf, back room, or bin

Follow the item’s physical path through the business: front shelf, overflow shelf, back room, receiving table, picking trolley, service counter, returns area, and quarantine space. Search temporary storage as well as the usual bin. Check behind other products and inside partly opened cartons. Assign one person to each area so searching does not produce another duplicate count.

Finding stock elsewhere changes the count only if that area belongs inside the comparison scope. Stock in a different workspace, goods owned by somebody else, or a shipment outside the agreed boundary cannot be added casually. Note where the units were found and whether they were counted earlier. A repeated back-room omission calls for a better area checklist, not a recurring loss adjustment.

Step 5 — check recent receiving

Match the purchase order, delivery evidence, actual receipt, and posted receipt record. A purchase order states an intention to buy; it does not prove the goods arrived. Confirm actual quantities received, short deliveries, partial cartons, duplicate postings, and documents still in draft or awaiting entry. Record the arrival time and posting time separately.

Check the direction of each correction. An unposted receipt normally makes the recorded balance too low; posting it increases that balance. It therefore does not, by itself, explain why physical stock is below recorded stock. If received goods were also excluded from the physical count, add them to the count only when they belong before the cutoff and inside scope. Update both sides consistently.

A supplier discrepancy is a request for evidence, not an accusation. Compare delivery quantities with the receipt count and investigate packaging or item mismatches before assigning responsibility. Where evidence is missing, leave the cause provisional and retain the supporting documents.

Step 6 — check sales and usage around the cutoff

Choose one reference time and bring both quantities to that time. Review sales, workshop issues, service consumption, picks, transfers, and other movements immediately before and after it. A transaction date and the time somebody posted it may differ. A physical movement belongs in the comparison according to the agreed cutoff policy, not simply because its record was entered today.

If movement cannot stop, keep a simple movement log with item, quantity, direction, time, and document reference. For a count taken after the snapshot, add documented inbound movements and subtract documented outbound movements from the snapshot to build the expected count-time quantity. Alternatively, roll the count back to the snapshot; do not use both approaches on the same movement.

Be especially careful with goods waiting at checkout, on a trolley, or at a workbench. Establish whether they were included physically and whether the relevant issue was already posted. The objective is one consistent comparison, not a convenient number that matches.

Sources: Oracle Inventory — Physical Inventory

Step 7 — check customer and supplier returns

A customer refund does not always mean a usable item returned to stock. Verify the physical item, SKU, condition, quantity, and disposition. A returned product may be waiting for inspection or disposal. Check whether it was counted and whether an inventory receipt was posted. Keep financial refund evidence separate from evidence of physical movement.

Supplier returns move goods out of the business. Inspect the return authorisation, dispatch evidence, and stock record rather than assuming a credit note proves dispatch. Goods packed for return may still be physically on site; clarify their stock status. Post a missing documented movement once, and avoid counting the same return in both a transaction correction and a general adjustment.

Step 8 — check write-offs, damage, and samples

Search the damaged-goods area and review disposal notes, expired stock, samples, demonstrations, internal use, and service consumption. Ask what physically happened and when. Damage may explain why goods are unavailable for sale while they remain present. A write-off may already have reduced the recorded quantity even if the goods await disposal; counting them as sellable would create a false excess.

Keep damaged units separate and record their status. If a documented write-off was omitted, correct it through the business’s approved process. If internal use or a sample issue was omitted, record that actual movement rather than disguising it as damage or theft. A reason code should describe evidence, not fill an empty field. Do not claim a tax deduction or create financial entries from this operational checklist.

Inventory Write-Offs: Damaged, Expired, Lost, Stolen and Unsellable Stock

Step 9 — decide whether an adjustment is justified

There are three different outcomes: correct the count, correct a specific transaction or identity record, or authorise a remaining stock adjustment. Prefer the specific correction when evidence identifies the mistake. Keep an adjustment proposal separate from approval. Set review thresholds suited to the business, considering units, value, repeated patterns, and risk; there is no universal acceptable discrepancy percentage.

The reviewer should see the original snapshot, recount evidence, movement review, supported corrections, revised comparison, and remaining difference. Check whether the system expects a new absolute balance or a signed adjustment quantity. Entering the wrong form can double a correction. After posting, verify the resulting balance and document reference, and check that no later transaction was accidentally overwritten.

An authorised correction can restore a usable stock record while the cause remains unknown. If that is necessary, label it as an unexplained count discrepancy under the business’s policy, with a named investigation owner. A zero remaining difference after an adjustment is not proof that the original root cause was discovered.

Sources: Oracle Inventory — Cycle Counting; Microsoft Learn — Cycle counting

Use root-cause categories that preserve uncertainty

Group findings by what the evidence supports: counting or scope error; unit or packaging error; SKU or barcode mapping error; storage or placement error; receiving or posting error; cutoff timing; customer or supplier return; documented damage, disposal, samples, or internal use; and unresolved difference. Each category should lead to a practical correction and a process owner.

True loss or suspected theft belongs in a separate review only after plausible count, identity, location, and transaction causes have been investigated. Even then, unexplained stock is not proof of who caused it. Preserve evidence, follow the business’s escalation process, and keep allegations out of routine count notes. More than one cause can contribute to a single discrepancy.

Worked case: 24 recorded, 19 counted, −5 variance

This illustrative case deliberately keeps an unresolved unit visible. At the agreed cutoff, the system shows 24 units. The first count records 19 sellable units on the front shelf, giving 19 − 24 = −5. The comparison should include all sellable stock on site, so the investigator searches the back room and receiving area before requesting an adjustment.

Two units found in the back room were missed, bringing the physical quantity to 21. One recently received unit, also missed in the first count, is found in the receiving area. Its receipt document was not posted, but the unit arrived before the cutoff. Including it brings physical stock to 22; posting the supported receipt increases recorded stock from 24 to 25.

Two other units had genuinely been damaged and disposed of before the cutoff, with evidence, but no write-off was recorded. They are absent from the physical count. The approved write-off reduces the recorded balance from 25 to 23. The final comparison before any unexplained adjustment is therefore 22 − 23 = −1 unit.

Bridge: physical 19 + 2 + 1 = 22 (front shelf, back room, and receiving). Recorded 24 + 1 − 2 = 23 (initial balance, receipt, and write-off). The original −5 changed by +2 for the back-room omission, zero net for a receipt missing from both sides, and +2 for the write-off correction, leaving −1. Keep that last unit unresolved pending further evidence or an authorised discrepancy adjustment.

Adding 2 + 1 + 2 and declaring all five units explained would be wrong: the unposted receipt also changes the recorded side. If the received unit had already been included in the original 19, the bridge would be different. State where it was physically counted. This example uses operational quantities only and does not invent accounting journal entries.

When repeated variance signals a process problem

Look for repeated causes rather than repeatedly resetting the same SKU. A recurring carton-size mismatch suggests a unit rule or receiving instruction problem. Paired shortages and excesses in similar variants suggest an identity check. Differences concentrated in a back room suggest incomplete area coverage. Timing differences after busy periods suggest that posting and physical movement are falling out of step.

Maintain a short issue register with item, date, original variance, supported cause, unresolved quantity, corrective action, owner, and follow-up date. Recount affected items after the process change and inspect whether the same mechanism recurs. Track unresolved cases separately from explained ones. More frequent cycle counts can shorten the investigation window, but they will not repair a bad unit conversion on their own.

Inventory variance versus shrinkage

Inventory variance describes a measured mismatch. Shrinkage describes loss within a defined business reporting approach; terminology and included causes vary. Counting error, cutoff mismatch, and a missed shelf can create apparent shortages without establishing physical loss. Documented damage or actual loss may need a separate classification under the business’s policy.

Do not turn every negative count into a theft metric. First reconcile quantities and separate supported movements from unexplained differences. Keep quantity investigation distinct from financial valuation. The shrinkage guide provides wider prevention context; this playbook helps establish whether a count difference represents a real loss, a record problem, or an incomplete investigation.

Recount and reconciliation checklist

Before closing the case, confirm: the SKU and variant match; the unit and pack conversion are verified; all included areas were checked once; damaged and reserved stock have an explicit status; both quantities refer to one cutoff; and a second count supports the physical total. Retain the original result even when it was wrong.

Then confirm: receipts were checked against actual arrival; sales and usage were reviewed; customer and supplier returns were traced; damage, disposal, samples, and internal use were reviewed; every correction has evidence and was applied once; any remaining adjustment has approval; and the resulting balance was checked. Name the owner of unresolved causes and schedule a follow-up count.

How Retail Scan & Stock can support the work

Retail Scan & Stock supports physical counts, receiving, write-offs, purchase-order work, and exports. Those documents can support an investigation alongside delivery evidence, sales or usage records, and the business’s review process. A purchase order helps trace a planned delivery; receiving records what actually arrived. An export can help a reviewer preserve quantities and document references.

These capabilities do not establish an automated root-cause engine or dedicated variance analytics. The investigator still confirms scope, identity, unit, cutoff, and evidence. Sales or usage records may come from another system. Use the same discipline with paper or a spreadsheet if that suits the business. Review plan information before choosing an app for the workflow.

Conclusion: correct the record and retain the explanation

A reliable reconciliation ends with a defensible physical quantity, a comparable recorded quantity, documented corrections, and a visible status for anything still unexplained. Start with the recount, test the mundane causes carefully, and let evidence determine the next action. A corrected balance is useful; a preserved explanation and a process fix make the next count more trustworthy.

Sources

Official references checked on October 3, 2026. The investigation sequence and worked case are editorial recommendations, not a mandatory accounting standard. Vendor documentation describes those vendors’ systems; it does not establish Retail Scan & Stock features.

• Oracle Inventory — Physical Inventory
• Oracle Inventory — Cycle Counting
• Microsoft Learn — Cycle counting
• SAP Learning — Conducting Inventory Counting and Inventory Posting
• GS1 — GTIN Management Standard

Frequently asked questions