Cycle Count Discrepancy Log: Investigate Before Adjusting Stock
A cycle count discrepancy log is a working record of a difference between a physical stock count and the inventory record for the same item, location, unit and comparison time. It keeps the evidence, investigation, approval and follow-up together so a team can explain what happened before deciding how to correct the record.
Cycle counting checks selected inventory repeatedly. Oracle’s cycle counting documentation describes its use for identifying recurring errors. The worksheet below is an original editorial template for warehouse supervisors and inventory controllers, rather than a required ERP form or a financial audit procedure.
What should the log contain?
| Field | What to record | Question it answers |
|---|---|---|
| Record and scope | Unique log reference; item code; warehouse and bin; batch or serial reference where applicable | Are we investigating the same stock? |
| Quantity basis | Count unit; verified pack conversion; record quantity; comparison timestamp | Are quantities comparable? |
| Count evidence | First count; recount; counter; time; linked count sheet | Can another reviewer reconstruct the observation? |
| Movement evidence | Receipts, picks, transfers and returns around the comparison time; document references | Could transaction timing explain the difference? |
| Review and decision | Possible cause; evidence supporting or rejecting it; reviewer; approved action reference | What justifies the action? |
| Prevention and closure | Action owner; due date; completion evidence; follow-up count | Was the process issue addressed? |
Keep candidate explanations separate from confirmed causes. An empty evidence field should remain visibly open; a label such as “human error” is not a substitute for a transaction reference or an observed process failure.
Before counting: agree on the comparison point
For this proposed workflow, the supervisor names the count scope, comparison time and person responsible for reviewing movements. Confirm whether the system permits stock movement during the count and how those movements will be reconciled. Microsoft’s Warehouse Management cycle-counting workflow does not automatically block the stock merely because counting work is open; this is product-specific behaviour, not a rule for every warehouse.
Check your own system configuration with its owner. Microsoft’s cycle counting documentation also explains unit conversion and review of counting differences. Recording a time without agreeing how receipts and picks affect the comparison can leave a well-completed sheet inconclusive.
Hypothetical example: two pieces apparently missing
Illustrative example, not HPA or client results: a training exercise defines one sealed box as 24 pieces. The record shows 100 pieces for item TEST-A in bin B-04 at 10:00. A physical count finds four full boxes and two loose pieces: (4 × 24) + 2 = 98 pieces. The preliminary difference is 98 − 100 = −2 pieces.
- Record −2 as the preliminary discrepancy, with the count time and pack conversion.
- Recount and check nearby locations, the item identity and any relevant tracking references.
- Inspect movement evidence. Suppose the exercise includes a documented pick of two pieces before the comparison time that has not yet been posted.
- If review confirms that timing explanation, the authorised team follows its procedure to correct the missing transaction. Avoid also posting an unsupported stock-loss adjustment for the same two pieces.
- If the evidence does not explain the difference, keep the cause unresolved and route it through the approved exception process.
The arithmetic is deliberately simple. The important output is a traceable decision: evidence reviewed, action authorised and a reference showing what was actually posted. This example does not prescribe accounting entries, tolerance levels or approval powers.
A short review meeting that produces actions
Use one open record in a practice meeting. Ask the counter to explain the observation, the reviewer to distinguish facts from hypotheses, and the process owner to propose a preventive action. Assign a person and date to each action. Marking a discrepancy “adjusted” should not silently mark its cause “solved.”
- Pack issue: confirm the product’s conversion and labelling before updating instructions.
- Movement issue: review when receiving, picking or transfer documents are posted.
- Location issue: agree how temporary staging locations are identified.
- Repeated unexplained issue: keep the evidence and escalation route visible rather than inventing a cause.
Useful questions
Does every discrepancy mean stock is lost? No. The log starts an investigation; the example above shows why transaction timing must be checked before attributing loss.
What tolerance should we use? Define it with the responsible operations and finance owners for your items, risks and system. This article supplies no universal acceptable percentage.
When is the record closed? For this template, close it only when the review decision, action reference and any agreed follow-up are documented. Keep prevention work open separately if it is unfinished.
Turn a recurring problem into a learning brief
For broader context, read HPA’s inventory management article. Professionals comparing learning options can review the published CPIM preparation course outline; confirm that the syllabus fits the role before booking.
For a team need, use HPA’s corporate training enquiry page and describe the participant roles and number, the recurring stock-record problem, the current system and a practical learning output—for example, completing and reviewing an anonymised discrepancy log. Confirm format, trainer, scope and fees with HPA. Do not send customer records or confidential stock details in an initial enquiry.


