What does negative inventory quantity mean in bookkeeping software?

The system has recorded more units sold (or consumed in assemblies) than it has recorded received. The physical goods existed — you shipped them — but the purchase or build that brought them in was entered late, against the wrong item, or not at all. The item's on-hand count goes below zero and its costing goes unreliable.

Does negative inventory affect cost of goods sold?

Yes, materially. Average-cost systems must guess a cost for units they have no record of owning, typically using the last known cost; when the real purchase posts later at a different price, COGS for the already-recorded sales is wrong and the software may post catch-up adjustments in the wrong period. Margins by item become untrustworthy.

How do I fix negative inventory quantities?

Fix causes before counts: enter missing or late item receipts with correct dates and costs, correct sales recorded against the wrong item or unit of measure, and record assembly builds before the sales that consume them. Then run a physical count and post an inventory adjustment for whatever residue remains.

Negative inventory: selling what the system thinks you don't have

Symptom

The inventory valuation report shows items at −14 on hand, sometimes with negative dollar value. Margins by item look erratic; COGS spikes in months with no unusual sales. The system happily kept selling units it had no record of ever receiving.

Why it happens

Timing. The sale posts today; the purchase that stocked it posts next week when the bill arrives (or when someone finally enters the item receipt). Between those dates the item is negative, and every sale in the window is costed on a guess.
Wrong-item entries. Received as "Widget-Blue," sold as "Widget – Blue" — two items, one physical product, one count climbing while its twin digs below zero. Unit-of-measure mismatches (bought by the case, sold by the each) do the same at scale.
Assemblies built on paper only. Finished goods are sold without recording the build, so the finished item goes negative while components sit untouched — or the build is recorded but a component was never received.
Uncounted shrink and samples. Damage, theft, and giveaways leave the shelves without leaving the books, so book counts run high until reality forces them under on paper later.

The dollar damage is in costing: average-cost systems invent a cost for the phantom units, then post catch-up corrections when the real receipt lands — often in a different period than the sales they correct.

The fix

List the negatives. Run quantity-on-hand for all items; export every negative row with its transaction history.
Repair timing first. For each negative item, find the purchase that physically stocked it and enter (or re-date) the item receipt to precede the sales it supplied, at actual cost. Watch the affected months' COGS move back toward sense.
Merge the twins. Where wrong-item or unit-of-measure splits exist, move the transactions onto one item and deactivate the duplicate; fix the unit definitions.
Record the missing builds for assemblies, dated before the sales that consumed the output, and verify component counts survive the rebuild.
Count and adjust. After causes are repaired, physically count the affected items and post an adjustment for the residue:

Journal entry — Inventory adjustment after physical count

Account	Debit	Credit
Cost of goods sold — shrinkage/adjustments	1,140
Inventory		1,140

Post through the software's inventory-adjustment function so item counts update — a bare journal entry fixes the GL but leaves the item ledger wrong. Direction reverses when the count finds more than the books.

Check the period damage. If the corrections materially moved COGS in a filed year, tell the preparer — inventory methods and year-end valuations feed the return (see IRS Publication 538 on accounting methods and Publication 583 on records).

How to prevent it

Receive before you sell. Enter item receipts the day goods arrive, even if the vendor bill comes later; every platform separates receipt from bill for exactly this reason.
Block or flag negative-quantity sales if the software offers the setting; where you must sell ahead of paperwork, make same-day receipt entry someone's named job.
Record assembly builds as part of the production routine, not at month-end.
Cycle-count the fast movers monthly and investigate any item that goes negative that month — one item is a process slip; a page of them belongs in the full triage of /bookkeeping/cleanups-fixes/books-cleanup-playbook. And when changing systems, bring counts from a physical count, never from the old file's fiction (/bookkeeping/cleanups-fixes/migration-cleanup-new-software).