Negative inventory: trace why on-hand stock went below zero

A receipt can restore the current balance while leaving a prior shift or reporting period with negative on-hand stock.

Kartik Deshpande··6 min read

Yesterday’s production issue took a component to -4 in the ERP. This morning, the balance is positive. To diagnose negative inventory, find the first transaction that took recorded on-hand below zero for that SKU and location. Then check whether the stock was there when the issue happened, using the receipt evidence and any corrections linked to that issue.

Start with the column that went negative. A report of stock available to promise can include commitments or expected supply. If you rebuild a physical balance from that column, you’ll carry allocation rules into a calculation meant to explain what was received and issued.

Find the stock measure that went negative

Write down the report column, cutoff, item, site, warehouse, and any bin, lot, or stock-status filters. Pull the physical on-hand and reserved quantities at that same scope. A warehouse total can mask a negative bin balance when another bin holds the same item. Stock at another site can cover a future transfer while leaving the original issue short at its own site.

Microsoft documents that Dynamics 365 Supply Chain Management subtracts physical reservations from physical inventory to calculate Available Physical. In that calculation, 11 units on hand with all 11 reserved leaves zero available. The reservation affects what can be assigned to another order. The units remain in stock until a movement removes them. Microsoft Learn’s on-hand definitions

If only the availability figure is short, start with the orders and holds that consume availability and the report’s treatment of expected receipts. The stock may be committed to other orders. The inventory allocation article covers what to do when several orders compete for the same usable units.

Trace the first negative balance through posted movements

Start with a verified ERP opening balance before the balance first went negative. If your opening row is already below zero, move the start date back. Export the transactions that changed on-hand after that opening, using the exact item and location scope from the report. Keep document and line IDs so two copies of an issue in overlapping exports count as one transaction.

Express movements in the same unit as the opening balance. Add receipts and transfers into scope. Subtract shipments, production issues, and transfers out. Retain the transfer reference on both legs, even when only one leg affects the balance you’re investigating. Microsoft documents signed quantities, receipt and issue statuses, and separate physical and financial dates in Dynamics 365 Supply Chain Management. Microsoft Learn’s inventory transaction fields

Keep a reversal on its own row with its sign, effective date, and reference to the original issue. A reversal of an issue increases recorded stock when it takes effect. Netting it into the original issue hides the quantity the ERP showed before the correction. Compare the issue and reversal against the material slip or shipping record to tell an entry correction from a real return to stock.

Use the dates and ordering rules for the balance you’re reproducing. When an export has dates without times, a row sort can invent an intraday dip. Use a documented transaction order where it applies or report the date-level balance and leave the intraday sequence open. NetSuite, for example, documents a transaction-type order for same-date costing. Oracle’s NetSuite costing documentation

Check when the receipt happened and when it hit the ERP

Trace inbound stock to a receiving log or warehouse scan, then to the ERP receipt line (including split receipts for a single purchase order line). An expected receipt date gives you the plan. The receiving record gives you evidence of when and where the units arrived. The ERP’s effective date puts the movement on the stock timeline. When the system records the entry time too, retain it so you can tell whether the original report had the row at all.

If the goods arrived before the issue and the receipt took effect afterward, preserve both dates when you hand off the timing exception. If the receiving record comes after the issue, look for another source of stock, such as a transfer with a missing inbound leg. When the evidence points to a different warehouse or lot, compare both scopes before using that receipt to explain the issue.

Worked example of a late receipt and a partial issue reversal

Assume one component, one warehouse, quantities in eaches, and no movements besides those shown. The ERP uses the dates below for its on-hand report. A signed receiving log shows that 12 units arrived Monday, and Tuesday’s signed material slip shows that production took seven units.

ERP eventSigned quantityRecorded on-handWarehouse evidence
Monday opening balance6 starting units6Opening record agrees with the stock on hand
Tuesday issue I-42-10-4Material slip shows seven units went to production
Wednesday reversal V-42 against I-42+3-1Corrects the issue quantity. No units came back.
Thursday receipt R-17+1211Receiving log shows the same 12 units arrived Monday

Tuesday is the first negative day in the ERP because the issue leaves 6 - 10 = -4 units. Wednesday’s reversal corrects the net issue to seven units and leaves the balance at -1 until the receipt takes effect. The warehouse records support 6 + 12 - 7 = 11 units after Tuesday’s issue. Thursday’s receipt closes the gap in recorded stock, while Tuesday and Wednesday still show negative balances.

Records behind the negative balance
Recorded balance

Opening quantity and signed ERP movements

Warehouse evidence

Receiving log and signed material slip

Exception for review

First negative date and matching document lines

Opening the receipt and issue documents together lets you distinguish a posting delay from a quantity error.

How Permute connects warehouse evidence to the ERP balance

Permute is the context layer we sell between business data and the AI tools people already use. We connect records from NetSuite and receiving logs kept in Excel, then use your mappings to match item and location IDs. A plant’s receiving sheet can then be reviewed beside its ERP receipt line when the records share a validated reference.

Set the stock scope, movement signs, and effective date rules once, so reports and AI tools use the same definitions. Keep the source references beside the result so a missing reversal link or unmatched receipt remains visible on review.

An inventory controller can ask in Claude or ChatGPT which issue took an item below zero and which receipt restored the balance. With the relevant data connected and access granted, the answer can include the dated transaction lines and any missing warehouse evidence.

Connect the records behind a stock balance

Start with the ERP export and receiving log for one warehouse, then review which document references the sources have in common.

Give the stock owner the evidence to review

Record the first negative balance, the issue and reversal references, the warehouse receipt evidence, and the date stock recovered. Assign the timing gap to receiving and the issue discrepancy to the production inventory owner. If the movement records cannot account for what’s on the shelf, use inventory reconciliation to compare a count with the ERP at one cutoff.

Flag any financial period the negative balance crossed for the controller. Oracle documents that NetSuite can estimate cost while an item is below zero and account for the difference when stock is received, so the receipt and the original sale can affect different periods. Send the original records through the authorized inventory and finance review before any correction to an ERP source record. Oracle’s NetSuite explanation of below-zero stock

Who owns changes to inventory records

We read from the systems we connect. Your authorized ERP users own changes to receipts, issues, and stock quantities. When warehouse evidence is missing or contradictory, the inventory owner still has to establish what moved before the controller can review any period impact.

Start a negative inventory investigation by confirming the stock measure and location. Rebuild the recorded balance to find the movement that took it below zero, keeping later reversals on their own dates. Check the receipt against the warehouse record to see whether stock was there when the balance went negative. Give the stock owner those references even if the current balance has recovered.

Review how inventory exceptions reach the controller

Bring the warehouse and ERP reports to an assessment to see where posting dates and document references get lost between systems.

Questions about negative stock balances

What if the oldest export already shows a negative balance?

Check for archived movements and an earlier opening balance for the same stock scope. If those records are unavailable, report the earliest date you can show was negative and leave the originating movement unconfirmed.

Can I tell how long inventory was negative if the ERP export has dates only?

You can identify days that end below zero if the export supports the daily balance. An exact duration within a day needs a reliable transaction sequence and timestamps. Separate the dates you can support from any intraday timing that remains unknown.