Locate the first unsupported inventory issue
Start with the earliest transaction that took the SKU below zero in the affected location. Review preceding receipts, transfers and sales in timestamp order. The cause may be a late receiving entry, an incorrect warehouse, a pack-size error or a duplicated inventory issue. A later positive quantity does not prove that the earlier transaction sequence and product cost are correct.
Save the original transaction history before making changes. Identify which transactions are operational records and which have reached the accounting ledger. A storefront quantity correction may repair availability while leaving a separate inventory system's valuation unchanged.
Check the costing system's actual behavior
Microsoft's inventory-costing guidance explains that negative inventory can cause issues to use a default price, or zero where no default is set, under specified costing configurations. It also warns that this can distort inventory value and gross margin. The exact effect depends on the system and method; obtain the configuration that applies to this item.
Ask the accountant whether a supported recalculation or inventory-close process is required after quantity corrections. Do not assume that adding the missing receipt automatically updates every earlier sales cost. Record which affected transactions the system recalculated and which still require review.
References: Microsoft: Inventory costing FAQ
Correct the event with evidence of when it occurred
If goods were received but the receipt was omitted, obtain the dated receiving evidence and approved purchase documents. If the wrong location was used, reconcile the paired location records. If the sale was duplicated, correct the duplicate through the integration's supported process. Each cause calls for a different correction, even when all initially produce the same negative number.
Do not backdate a receipt solely to remove an inconvenient balance. The accountant should assess the actual event date, closed-period policy and reporting impact. Preserve the correction date and the reason so a reviewer can understand how the historical record changed.
Recheck the affected margin calculation
Suppose a hypothetical sale of ten units generated $300 of revenue but initially carried zero product cost because the relevant receipt was missing. If the supported unit cost is $12 and the approved correction assigns it to those units, the omitted product cost is $120. The original $300 product margin becomes $180 before other selling costs.
Use that example as a diagnostic calculation, not an instruction to post $120 without examining the accounting system. Some systems create later cost adjustments, and other methods behave differently. Reconcile the resulting product cost to the ledger after the supported correction runs.
Fix the process that let the sequence break
Compare the recurring time gap between receiving goods, entering receipts and releasing customer orders. A warehouse may ship usable goods before finance has the supplier invoice, but the system still needs a supported receiving and costing process. Agree who records the receipt and what estimate or default the accountant permits while final costs are outstanding.
Monitor negative quantities by duration and value at risk, with repeated locations or SKUs assigned to an owner. Close an exception after both quantity and valuation have been reviewed. A zero-or-positive stock balance alone is insufficient evidence that the margin from the affected sales is now reliable.
Sources
Requirements and product details can change. Check the linked guidance for the facts that apply to your situation.
Related reading
Need help with this work?
General information, not personalized accounting, tax, legal, or investment advice. Have the appropriate qualified professional review decisions that depend on your circumstances.