A negative on-hand balance on a stocked part means the ledger records more issued than received, which physical stock cannot do: the cause is either a consumption posted ahead of its matching receipt, or a starting quantity that was never entered. EDGEBIC by User Solutions flags it as a warning on the plant-wide anomaly scan rather than blocking anything, because the temporary version is normal bookkeeping and the permanent version is a data gap.
Telling those apart is the whole job. This post covers both shapes, how to correct the real one, and why the correction is a posting rather than an edit. It sits with the other inventory symptoms in the EDGEBIC troubleshooting guide. For the ledger itself see how to audit the inventory ledger for a part, and for the different problem of a balance disagreeing with its ledger see my on-hand quantity does not match the inventory ledger.
What You Are Seeing
A part shows a balance below zero. A plant-wide anomaly scan lists it as a warning saying more has been issued than received. The shop floor may or may not agree: sometimes the shelf is genuinely empty and the number is honest, and sometimes there is stock sitting there that the system has never known about.
Why It Happens
Cause 1: A Consumption Posted Ahead of Its Receipt
The common and usually harmless case. A job draws stock, the consumption posts immediately, and the build that will replenish that stock has not completed yet so its receipt has not landed. Between those two moments the balance can dip below zero.
How to tell: the negative appears and then clears, and there is an in-progress build for the same part.
Cause 2: A Starting Quantity Was Never Entered
The permanent case. The plant physically held stock when the part was set up, no opening balance was posted, and the ledger therefore begins at zero. Every issue since has driven the total further down while the shelf stayed full.
How to tell: the negative persists, grows steadily, and the physical count contradicts it outright.
Cause 3: A Receipt Was Reversed and Not Replaced
The ledger never deletes: a receipt that was wrong is corrected by a reversal, which puts the quantity back out of the balance. If the corrected receipt was never posted afterwards, the balance stays short by that amount.
How to tell: the history shows a receipt and a matching reversal with nothing following them.
A Case That Does Not Fire This Check
A part that is not flagged as stocked can carry a negative total without being reported, because it does not hold physical stock in the first place. If you expected a warning on such a part and did not get one, that is the reason, and the stocked flag itself may be what needs attention. See a make-to-stock product cannot hold inventory.
How to Fix It
- For a temporary dip, do nothing. The receipt lands when the build completes and the balance recovers. Posting an adjustment each morning fabricates stock and then double-counts it.
- For a missing starting quantity, count the shelf and post it. An opening balance or an adjustment for the physical figure brings the total to reality.
- Give every correction a reason line, for example a cycle count correction and its date. A year later that line is the only thing that explains the entry.
- Never edit the number directly. Corrections are postings, which is what keeps the ledger usable as a trail, and the mechanics are in how to make an inventory adjustment.
- For an unreplaced reversal, post the corrected receipt rather than adjusting around it.
How to Diagnose It, in Order
- Run a plant-wide anomaly scan. This check does not appear on a job-filtered run.
- Open the transaction history for the flagged part and read it in date order.
- Look for an in-progress build that will receive against the part. If one exists, the negative is probably timing.
- Count the physical stock. A full shelf against a negative total settles it immediately.
- Post the correcting entry with a reason, then re-scan to confirm the row cleared.
Why This Is Not the Same as Cache Drift
Two inventory findings look alike and are not. Drift means the stored on-hand figure and the ledger total disagree with each other, so one of them is wrong and the ledger is the one to trust. A negative balance means the two agree and the agreed number is impossible, so something that physically happened was never recorded. The first is a synchronization problem; the second is a missing movement. Reading them as the same thing leads to adjusting a number that was never the problem.
How to Prevent It
- Post opening balances at setup, for every part the plant already holds. Most permanent negatives trace back to this one omitted step.
- Check parts from the same setup batch when you find one, because this failure arrives in groups rather than alone.
- Scan plant-wide on a rhythm, not only when something looks wrong. A negative that has been growing quietly for a month is far harder to reconstruct than one caught the week it started.
- Keep reversals paired with their replacements. A reversal is only half a correction until the right entry follows it.
It means the ledger records more issued than received for a stocked part, which physical stock cannot do. The usual explanation is timing rather than error: a consumption was posted for a build that will receive later, so the balance dips below zero until that receipt lands. The other explanation is a missing starting quantity, where stock the plant physically holds was never entered, so every issue drives the total further down.
No. A temporary negative caused by a consumption posting ahead of its matching receipt corrects itself when the build completes and receives. That case needs no action. A negative that persists across days, or that grows steadily, is a real gap: usually stock that exists on the floor but was never entered as an opening balance. Watch the direction over a few days before deciding which one you have.
Post an entry rather than editing the number. The ledger is append-only by design, so the correct move is an opening balance or an adjustment that brings the total to the real figure, with a reason line stating what it is, for example a cycle count correction and its date. Never delete an entry to make a balance look right, and reverse rather than remove when an entry itself was wrong. The trail is what makes later drift explainable.
Expert Q&A: Deep Dive
Q: One part shows minus forty on hand and the shelf clearly has stock. What is the likely cause?
A: Most often the starting quantity was never entered. If the plant was already holding that part when it was set up, and no opening balance was posted, the ledger begins at zero and every issue since has pushed it below. Count the shelf, then post an opening balance or an adjustment for the physical figure with a clear reason. The balance corrects and the trail records why. Check whether other parts from the same setup batch have the same shape, because this failure usually arrives in groups.
Q: Our negative appears for a day and then clears every time. Should I still do something?
A: Probably not to the ledger, but it is worth understanding. A consumption posted before its matching build receipt lands produces exactly this pattern, and the dip is real bookkeeping rather than a defect. If the daily dip makes reports harder to read or worries a buyer, look at the sequencing of the build and the consumption rather than at the balance. The one thing not to do is post an adjustment each morning, because that fabricates stock and then double-counts it when the receipt arrives.
Frequently Asked Questions
Ready to Transform Your Production Scheduling?
User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.
User Solutions Team
Manufacturing Software Experts
User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.
Share this article
Related Articles
An Operation Moved and the Machine Was Free: Finding the Hidden Cause
A job slid and every machine shows open hours. Tooling is the cause the Gantt cannot draw. How to rule it in or out in two minutes before you chase calendars.
An Operation Shows Running Forever Though All Hours Are Logged
A step stays in progress after every hour is logged because completion is an explicit stamp, not an hours threshold. How to close it and stop it recurring.
Another User Changed This Record: Causes and Fixes
EDGEBIC refuses a save when the record moved after you loaded it. The usual cause is a colleague, but the message also appears when you are alone. How to read it and what to do.