What it means
Inventory systems track receipts, transfers, sales and returns, so if one transaction is missed or the physical count differs, the ledger and warehouse record can drift apart. A manual adjustment may be needed, but it changes both stock available for customer orders and potentially the business's financial results.
A clear approval route prevents one person from creating a favourable balance without review. Start with a count or other evidence: record the item, location, lot or serial number, system quantity, physical quantity, unit cost and proposed reason, and recount material differences with a second person where practical.
Check pending receipts, unposted transfers, returns and pick transactions before deciding stock is truly missing or extra. An item in a quality-hold area should not be adjusted into sellable stock just because the total count matches.
Understand the type of change, because a quantity adjustment differs from a valuation write-down for damaged or obsolete items, and a transfer between bins may correct location without changing total stock. The accounting policy and item status determine the entry, so a warehouse supervisor may confirm a physical difference while finance approves its valuation and reporting treatment, with roles and thresholds explicit.
Use reason codes that reflect what happened, not a generic "correction", since damage, expiry, counting error, unrecorded movement and suspected theft need different follow-up, and do not accuse staff or suppliers solely from a variance. If a high-value item is missing, preserve records and escalate through the appropriate security and management route, restricting sensitive conclusions to those who need to know.
Approve before posting when possible; emergency changes may be necessary to stop an incorrect shipment, but a retrospective review should be prompt and documented, and system permissions should prevent a person from entering, approving and hiding a large adjustment without oversight. Keep the original transaction, proposed change, approver and timestamp in the audit trail, and avoid deleting history to make the stock figure look neat.
After posting, check dependent orders and reports, because a reduction may make a promised order impossible so sales should be informed, and an increase may make stock appear available when inspection is still needed. Finance should reconcile the inventory subledger to the general ledger and review material adjustments at period-end.
Trend analysis by SKU, site and reason can point to receiving, picking or shrinkage problems. For owners, the control keeps inventory and profit credible.
Good approval is not a refusal to correct errors; it is a reliable way to correct them and learn why they occurred.
In practice
Real-world examples.
Example
A cycle count finds eight fewer units than the system. Staff recount, check transfers and submit a documented adjustment for approval.
Example
A damaged batch remains physically present but is not sellable. Warehouse and finance review its status and valuation rather than simply deleting quantity.
Example
A return was put away without scanning. The team records the missing receipt instead of posting an unexplained positive stock adjustment.
Formula
Calculation
Quantity adjustment value = Approved quantity difference x Applicable unit carrying cost
Worked example. An invented count confirms five units missing from stock recorded at $80 each.
- Adjustment value = 5 x $80 = $400 decrease, subject to the accounting policy and investigation.
- If the units were merely moved to another bin, correct the location rather than reducing total inventory.
For mixed-cost or lot-specific goods, use the correct valuation method rather than one arbitrary unit price.Case study
Seen in the real world.
This illustrative and entirely fictional example follows Maple Electrical, an invented distributor. Its warehouse staff regularly adjusted stock when the picking screen showed an empty bin. Finance saw a growing number of small negative entries but no clear reasons. A physical review found that many items were in an overflow area without system transfers; other differences came from unrecorded damage. Maple introduced a threshold-based approval process.
Pickers logged exceptions, inventory staff checked nearby locations and recent movements, and supervisors approved small supported corrections. Finance reviewed larger or valuation-affecting changes. The team fixed overflow labelling and required damage to be moved into a separate status with evidence. The number of manual adjustments fell, and the remaining entries had usable causes. The owner could distinguish real shrinkage from location errors and make customer promises from a more trustworthy stock record.
Watch out
Common mistakes.
- Posting adjustments before checking pending transactions and nearby locations.
- Using a generic reason code that hides repeated receiving or picking problems.
- Letting one user make and approve significant changes without an audit trail.
Questions
People also ask.
Does every count difference require an adjustment?
Verify the difference first; it may be a timing, location or transaction error that needs a different correction.
Who should approve it?
Follow value and risk thresholds, with finance involved for material valuation effects and separate review where practical.
What happens after approval?
Update affected orders and ledger records, and analyse the cause so the same difference does not recur.
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%