What it means
A cycle count finds 96 units on a shelf while the inventory system says 100, so before reducing the record a supervisor checks transactions and asks for a recount. An approval control keeps a count difference from becoming an unsupported adjustment.
Oracle inventory guidance describes tolerances, recounts and held adjustments, and its warehouse rule documentation shows configurable approval based on quantity or value, but these are system options, not universal legal thresholds. Define the count scope, since item, lot, serial number, location and unit of measure matter and a count of cases compared with pieces can create a false variance.
Record expected and observed quantities with the snapshot time, because goods moving during the count can change the balance before approval. Investigate unposted receipts, picks or transfers first, since correcting the transaction can be better than a manual stock adjustment.
Choose a recount rule: high-value or large differences may require independent verification, and a recount should not simply copy the first number. Use tolerances thoughtfully, because a small quantity difference on a costly item may be material while an absolute threshold could miss it, so consider both quantity and value.
Separate preparer and approver when practical, so the same person does not count, post and approve a material adjustment, and small businesses can use compensating review. Capture a reason and link evidence, because damage, theft, unit conversion and location error call for different follow-up, a generic adjustment code hides causes, and count sheets, scans, photos and transaction review can support the decision, with sensitive details kept in controlled systems.
Preserve original values so the record shows the before quantity, count result, approved change and posting time, since overwriting one field removes auditability. Check lot status too: if stock is quarantined or expired, changing quantity does not authorise release, and quality controls remain separate.
Review value, because finance may need the cost impact and accounting period and a quantity correction can affect inventory valuation. A count at month-end with a later approval can raise period questions, so follow the accounting close policy instead of backdating casually.
Check negative quantities, since some systems allow them temporarily but an unexplained negative balance is not a valid physical count, and prioritise safety by never reaching into unsafe racking or moving hazardous goods just to finish the count. Limit who can approve and post adjustments, review roles periodically including service accounts, record whether rejected counts need a recount or transaction fix, and give held adjustments a deadline and escalation route, because a held adjustment can leave stock unavailable or inaccurate.
Escalate repeated differences, since frequent errors in one aisle may reflect poor scanning or layout, and one adjustment may be harmless error while recurring loss may need security and process review without assuming theft. Auto-approval under a configured tolerance is still a control choice, so test the rules, audit a sample against count evidence, recheck reservations and customer commitments after posting, and train staff on unit conversions, pending transactions and lot statuses; for owners, approval protects inventory records from guesswork and should help teams correct the real cause, not merely make the system match a shelf.
In practice
Real-world examples.
Example
A four-unit shortfall on a shelf triggers a recount before posting. The second counter, who has not seen the first result, also finds 96 units, so the team moves on to check open transactions.
Example
An unposted transfer explains a location difference without changing total stock. The supervisor posts the transfer and closes the variance rather than approving a manual stock adjustment.
Example
A high-value adjustment receives independent review and a documented reason. Finance reviews the cost impact and the accounting period before the posting is released.
Formula
Calculation
Quantity variance = Physical count - System balance. Value of variance = Quantity variance x Unit cost.
Worked example. A cycle count finds 96 units against a system balance of 100, and the item costs $25 per unit.
- Quantity variance = 96 - 100 = -4 units.
- Value of variance = -4 x $25 = -$100.
- If an approval rule requires a recount for any difference of more than 3 units or $50, both triggers are met here, so a recount and a transaction check come before any posting. If the recount still shows 96 and no open transaction explains the gap, the $100 decrease can go for approval.Case study
Seen in the real world.
This entirely fictional case follows Cedar Parts. A count showed a shortage in one location, but a pending transfer had already moved the stock. The team posted the transfer rather than an adjustment and refined its count cutoff. The case does not prescribe a universal approval tolerance.
After the first incident, Cedar Parts reviewed the previous quarter's held adjustments. Several had sat unapproved for weeks, leaving stock unavailable to sales while nobody owned the decision. The company gave each held item a deadline and an escalation route, and it sampled posted adjustments against count sheets to check the evidence was real. The changes improved the quality of its records, though the illustrative result does not show that every future count will be free of error.
Watch out
Common mistakes.
- Posting a count difference without checking open transactions.
- Using a generic reason for repeated unexplained losses.
- Treating adjustment approval as removal of a quality hold.
Questions
People also ask.
Why approve count adjustments?
To verify evidence and control changes to inventory records.
Should every difference be posted?
No. Recount and transaction review may explain it.
What thresholds apply?
Use site risk, value and configured controls; no universal tolerance fits all.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%