Oracle Cloud Inventory study materials
Oracle Cloud Inventory study resources

Cycle Count Variance on a Standard-Cost, Lot-Controlled Item

Oracle Cloud Inventory · Put your knowledge to work in context.

All case studies

Cycle Count Variance on a Standard-Cost, Lot-Controlled Item

At a semiconductor plant, item WAFER-200 is standard-costed at 18 USD per unit. The book balance is 500 units in subinventory PROD, locator A-01. A cycle count of that locator records 450 units. The counter notes two lots: lot L2401 with 300 units and lot L2312 with 150 units; L2312 expired two weeks ago. There is an open miscellaneous transaction for 25 units pending approval, and a move order to PROD for 50 units that was picked but not confirmed. The count was taken on the last day of the period. The cost accountant wants to post a 50-unit adjustment immediately to close the period. The item is lot-controlled and shelf-life-controlled, and the organization uses standard costing. Last month the same locator had a 40-unit variance that was written off without investigation.

1. Before posting the adjustment, what would you investigate and in what order? Explain how each item could explain the 50-unit difference.

Read the worked answer

Investigate before adjusting. First, confirm the count itself: was locator A-01 counted blind, was every lot counted, and was the count recut? Second, review open transactions that affect the locator. The 25-unit miscellaneous transaction pending approval could add 25 units if approved, and the 50-unit move order picked but not confirmed could add 50 units if it is a receipt into PROD or remove 50 if it is a pick out. The direction of the move order matters. Third, reconcile at lot level: 300 plus 150 equals the counted 450, so the variance is not obviously a lot mix-up, but the expired lot L2312 must be examined because expired material may belong in a different subinventory or may have been excluded from availability. Fourth, check transaction timing at period end and whether the count occurred before or after cutoff.

The prior 40-unit write-off without investigation is a red flag for a recurring process problem, not proof that the current variance is acceptable. The 50-unit difference may be entirely explained by the pending transactions, or it may be a genuine shortage. Do not post the adjustment until open transactions and lot status are resolved.

2. If a 50-unit adjustment is required, analyze the costing and lot impact under standard costing. How would your answer differ under average costing?

Read the worked answer

Under standard costing, the adjustment is valued at the standard cost of 18 USD per unit, so a 50-unit write-down is 900 USD, posted to the appropriate inventory adjustment or variance account. The standard cost itself does not change. Because the item is lot-controlled, the adjustment must be made at the lot level, not just the locator quantity. If lot L2312 is expired, consider whether the correct action is an expired-stock write-off, a move to a reject or expired subinventory, or a separate disposition, rather than blending it into a generic cycle count adjustment. The expired lot may require its own approval and expense treatment.

Under average costing, the adjustment is valued at the current average cost of the item, and the write-down reduces inventory value at that average. If the organization is average-costed, the adjustment does not create a standard-cost variance in the same way, but it still affects the average cost if quantities and layers change. In both cases, obtain approval above the defined threshold and require a reason code. The costing difference matters for the journal entry and for management reporting, but it does not remove the need to resolve the lot and transaction questions first.

3. Recommend controls to prevent repeat unexplained variances at this locator.

Read the worked answer

Treat locator A-01 as a higher-risk location because it has a repeat variance. Increase its cycle count frequency and use blind counts. Establish a transaction cutoff before counting and reconcile open move orders, pending miscellaneous transactions, and pending approvals before the count is finalized. Restrict access to the locator and segregate count entry from adjustment approval so the counter cannot approve their own variance. Set a variance threshold that triggers investigation and requires a reason code, with escalation for repeated variances at the same locator or item.

Add lot and shelf-life reports to the daily routine so expired lots are moved or disposed of before they distort counts. Review the prior 40-unit write-off and the current 50-unit difference together; if both involve the same locator, look for a process cause such as unconfirmed move orders, informal physical moves, or picking without system confirmation. Track adjustment trends by locator, item, and reason code, and feed the results back to warehouse supervision. The goal is not to eliminate all adjustments but to ensure every adjustment is explainable and approved.