8.6 Inventory Record Accuracy, Cycle Counting & Excess Disposition

Key Takeaways

  • Inventory record accuracy is measured by location and part against a tolerance, not by comparing total inventory value, because offsetting errors conceal each other in a value comparison.
  • Cycle counting counts a subset continuously by ABC frequency and finds and fixes root causes; an annual physical inventory only corrects the book balance once a year.
  • A record error is a process failure, so every count discrepancy should trigger root-cause investigation rather than only a book adjustment.
  • Excess and obsolete inventory should be dispositioned on a defined ladder from internal reuse through return, resale, and donation to scrap, with write-off recognized when the value is impaired rather than when the goods are physically removed.
  • Shrinkage arises from theft, damage, misplacement, and transaction error, and transaction error is usually the largest and most correctable component.
Last updated: August 2026

Inventory Record Accuracy, Cycle Counting & Excess Disposition

Every model in this chapter — economic order quantity, reorder point, safety stock, MRP netting, multi-echelon positioning — consumes one input: the inventory record. If the record is wrong, every downstream calculation is wrong, and no amount of modelling sophistication rescues it. This is the least glamorous and most consequential topic in materials management.


Measuring Accuracy Correctly

Inventory record accuracy (IRA) is the percentage of records where the counted quantity matches the system quantity within a defined tolerance:

IRA=Records within toleranceRecords counted×100\text{IRA} = \frac{\text{Records within tolerance}}{\text{Records counted}} \times 100

Three rules the exam tests:

  1. Measure by part and location, not by total value. A location holding 60 units where the system says 50, and another holding 40 where the system says 50, net to a perfect total value with two wrong records and two future stockouts. Value comparison hides exactly the errors that cause operational failure.
  2. Define tolerance by item, and keep it tight. Tolerances are typically zero for serialized and high-value items and small percentages for bulk or weight-counted material. A tolerance loose enough to pass everything measures nothing.
  3. Count the location, not the item across locations. An item that is right in total but in the wrong location will still fail a directed pick.

Typical targets: 99%+ for A items, 97–98% for B items, 95%+ for C items — and 100% for serialized, lot-controlled, regulated, or hazardous material where traceability is a legal obligation rather than an efficiency measure.

What Inaccuracy Actually Costs

  • Stockouts on items the system says are available — the most damaging outcome, because no replenishment was triggered.
  • Excess inventory from ordering against understated on-hand.
  • Expediting and premium freight to recover from surprise shortages.
  • Lost productivity — pickers travelling to empty locations, and searches that consume more time than the pick.
  • MRP degradation — inaccurate on-hand quantities corrupt every netting calculation down the bill of material.
  • Loss of user trust, after which planners build private spreadsheets and informal buffers, and the formal system quietly stops governing anything.

Cycle Counting vs. Annual Physical Inventory

Annual physical inventoryCycle counting
FrequencyOnce or twice a yearContinuous, every working day
DisruptionOperations typically shut downNone — counts run during normal work
Who countsOften borrowed staff unfamiliar with the materialTrained regular staff who know the items
Error detectionUp to twelve months after the error occurredWithin days or weeks
Root causeEffectively impossible to traceTraceable while the trail is still warm
Primary outputA corrected book balanceA corrected process
Accuracy trajectoryResets annually, then decaysImproves continuously

The core exam point: cycle counting's purpose is not to adjust the books. It is to find and eliminate the process failures that create errors. An organization that counts diligently and adjusts every discrepancy without investigating causes will count the same errors forever. The adjustment is the symptom; the root cause is the deliverable.

Designing the Program — ABC-Based Frequency

ClassShare of valueTypical count frequencyCounts per year
A~70–80% of value, ~10–20% of itemsMonthly or quarterly4–12
B~15–20% of valueSemi-annually2
C~5–10% of value, ~50%+ of itemsAnnually1

Worked sizing. A facility holds 6,000 SKUs: 600 A items counted 12 times a year, 1,400 B items counted twice, and 4,000 C items counted once. (600×12)+(1,400×2)+(4,000×1)=7,200+2,800+4,000=14,000 counts per year(600 \times 12) + (1{,}400 \times 2) + (4{,}000 \times 1) = 7{,}200 + 2{,}800 + 4{,}000 = 14{,}000 \text{ counts per year} Across 250 working days that is 56 counts per day — a workload that must be resourced deliberately, not absorbed as an afterthought. A programme designed without this arithmetic is abandoned within a quarter.

Trigger-based counting supplements the schedule: count when the balance reaches zero, when a negative balance occurs, when a pick shortage is reported, after a cycle-count adjustment on a related item, and when an item is received or issued for the first time in a long period. Zero-balance counting is particularly efficient because verifying an empty location is fast.


Root Causes of Record Error

Root causeTypical mechanismCorrection
Transaction errorWrong quantity keyed, wrong part number, transaction not recorded, recorded twiceAutomatic identification — barcode or RFID scanning removes keystroke error entirely
Unrecorded movementMaterial taken from a location without a transaction; production pulls without backflushPhysical access control; disciplined issue process
Timing differencesPhysical move recorded in a different period from the countCount cut-off discipline; freeze transactions during the count
Receiving errorsSupplier ships a different quantity than the packing list states; over- or under-receiptReceiving verification; supplier packing accuracy on the scorecard
Unit of measure confusionEach versus case versus pallet mismatchesMaster data discipline; UOM validation at transaction entry
Damage and scrap not recordedMaterial destroyed but never written offScrap transaction discipline
Theft and pilferageInternal or external lossAccess control, surveillance, segregation of duties
MisplacementMaterial stored in an undirected locationDirected put-away; location verification scanning

The correctable majority: in most manual operations, transaction and process errors substantially exceed theft as a cause of record inaccuracy. Organizations that treat every discrepancy as a security problem invest in surveillance and miss the far larger and cheaper win available from scanning, directed put-away, and issue discipline.


Excess and Obsolete Inventory Disposition

Excess inventory is more than foreseeable demand requires; obsolete inventory has no foreseeable demand at all. Both are identified by aging analysis — value by months of supply and by months since last movement — and both must be actively dispositioned, because inventory that is never reviewed is never written down and quietly overstates the balance sheet.

The Disposition Ladder, Highest Recovery First

  1. Redeploy internally to another plant, region, or business unit that has demand.
  2. Return to supplier under a stock rotation, buy-back, or return-for-credit clause — which only exists if it was negotiated into the agreement in advance.
  3. Use in service, spares, or warranty applications.
  4. Rework or upgrade into a currently saleable configuration.
  5. Sell through secondary markets — brokers, liquidators, surplus auctions.
  6. Sell to employees or discount channels, where brand policy permits.
  7. Donate for the applicable tax treatment.
  8. Recycle or reclaim material value.
  9. Scrap — the last resort, and for regulated or brand-sensitive goods a certified destruction with documentation.

Accounting reality the exam expects: the loss occurred when the inventory became unsaleable, not when it is physically removed. Under lower-of-cost-or-net-realizable-value principles, impaired inventory should be written down when it is identified. Delaying the write-off to avoid recognizing the loss keeps overstated assets on the balance sheet and — more damagingly for supply management — leaves the material occupying space, consuming cycle-count effort, and hiding the demand-planning failure that created it.

Preventing the Next Batch

  • Aging reports reviewed on a fixed cadence with a named owner and an action decision on each line.
  • Negotiated return and stock-rotation rights in supply agreements, particularly for distributors and for items with obsolescence risk.
  • Cancellation and liability windows defined at contract signature, so a demand change does not automatically become a raw-material liability.
  • Phase-out planning synchronized to component lead times, as covered in life-cycle management.
  • Root-cause review of each write-off — was it a forecast failure, a phase-out planning failure, an engineering change, or a minimum-order-quantity artefact? Each has a different and correctable remedy, and the disposition is worth nothing if the cause survives.
Loading diagram...
Cycle Counting as a Root-Cause Engine
Test Your Knowledge

A warehouse manager reports 100% inventory accuracy because the total value of counted inventory matched the system value exactly. A subsequent audit finds numerous individual location discrepancies. What measurement error was made?

A
B
C
D
Test Your Knowledge

A facility holds 6,000 SKUs and plans to cycle count 600 A items twelve times a year, 1,400 B items twice, and 4,000 C items once, across 250 working days. What daily workload does this imply, and why does the calculation matter?

A
B
C
D
Test Your Knowledge

A cycle counting program has run for two years. Counts are performed diligently and every discrepancy is adjusted in the system, yet accuracy has not improved. What is missing?

A
B
C
D