Module 8 · Control + audit proof

Physical Inventory, Cycle Counts & Discrepancies

Physical inventory procedures, cycle counting, count sheet creation, inventory differences, recounts, root-cause analysis and discrepancy handling.

Course reading

Understand the process

Part 1

Why counting matters

Book stock is what the system says is present; physical stock is what can actually be counted. Differences arise from missed movements, wrong bins, damage, unit-of-measure errors and timing. A full annual count detects problems late; cycle counting checks selected items throughout the year without stopping everything at once.

An ABC plan often counts high-value or fast-moving A items more frequently than lower-impact C items. Before counting, freeze or carefully record movements so the count and system snapshot refer to the same moment. Count the item, bin, batch and unit of measure, not just a total number.

Part 2

Investigate before adjusting

Suppose the system says 100 units but a bin contains 92. Recount with a second person, check nearby bins, open picks, receipts and recent transfers. If eight units were issued physically but the posting was missed, the fix includes correcting the process at issue, not just changing the balance to 92.

Record the approved adjustment, root cause, owner and preventive action. Repeated discrepancies on one item usually indicate a broken handover or measurement method. A clean audit trail explains both the final quantity and why the original number was wrong.

What you must take away

  • Count accuracy is a process measure — the adjustment value is only the symptom.
  • Recount before you post. The first difference is usually a location or unit error.
  • Counting everything once a year finds errors twelve months too late.

In the SAP process

  1. Create the physical inventory document and block the relevant bins for movement.
  2. Enter counts, then trigger a recount for differences beyond tolerance.
  3. Post the difference with a reason code and keep the signed count sheet.

Case study

The annual count that stopped the plant for two days

Setting. A store with 6,000 line items counting once a year with contract labour.

Problem. The annual count produced a large write-off, two lost production days and no information about what had actually gone wrong.

How it was investigated

  • Classified the difference value by material group and by movement frequency.
  • Found most of the value sat in a small number of fast-moving, high-value items.
  • Found unit-of-measure confusion on items bought in boxes and issued in pieces.

What was changed

  • Replaced the annual count with ABC cycle counting: A items monthly, B quarterly, C yearly.
  • Standardised units of measure and relabelled the affected bins.
  • Made every difference above tolerance require a recount plus a written root cause.

Outcome. Differences were found within weeks instead of at year end, and the plant stopped shutting down to count.

Lesson: Count the items that move, often. Count the rest rarely. Never count everything at once.

Illustrative composite of common shop-floor situations — no client names or confidential figures.

Practical template

ABC cycle count plan and discrepancy log

Schedule counts by value and record the root cause of every difference.

ClassCount frequencyMaterialSystem qtyCounted qtyDifferenceRoot causeAction
AMonthlyMAT-1042480462-18Issued without postingRetrain, daily posting cut-off

How to use it

  • A = top 80% of consumption value, B = next 15%, C = remaining 5%.
  • Count accuracy % = lines within tolerance ÷ lines counted. Track it, not the rupee value.
  • Root cause must name a process step, never a person.

Quick quiz — check your understanding

  1. 1. Physical inventory is:

  2. 2. ABC classification for cycle counting means:

  3. 3. A stock discrepancy is:

  4. 4. Common causes of discrepancies include:

  5. 5. Blind counting means: