# Business Central: "You have insufficient quantity of Item on inventory" > Source: https://netray.co/erp-help/bc-insufficient-quantity-of-item-on-inventory-error > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer Business Central raises this error when posting would take an item negative and Prevent Negative Inventory is switched on, either globally in Inventory Setup or on the item card. The usual root causes are a different location or variant than you expect, an earlier posting date, receipts not yet posted, or lot or serial numbers that are not available. Check the item ledger for the exact combination before changing the setting. ## Kind error ## System dynamics ## Erp Microsoft Dynamics 365 Business Central ## Module Inventory / Item Ledger ## Query You have insufficient quantity of Item on inventory Business Central ## Alternate Queries - business central prevent negative inventory error - business central cannot post shipment insufficient quantity item - business central allow negative inventory item ledger ## Applies To Business Central online and on-premises, Dynamics NAV 2013 and later ## Steps ### How to find and fix the shortage **Items:** - Note the item number, location code and variant on the failing line. Inventory is checked per item, variant and location combination, not item total. - Open the Item card, then Item Ledger Entries, and filter by that location and variant. Sum Remaining Quantity on open entries to see the real balance. - Compare the posting date on the document to the dates of the inbound entries. Posting an issue dated before the receipt date can show as negative for that date. - Look for receipts that exist as documents but are not posted: purchase receipts, production output, transfer receipts. Post them first if they are genuine. - If the item is tracked, open Item Tracking Lines and confirm the lot or serial numbers you selected have remaining quantity at this location. - Check warehouse setups. With Bin Mandatory on the location, quantity must exist in a bin the pick or shipment can use, otherwise you hit warehouse errors before or alongside this one. - Check Inventory Setup and the item card for Prevent Negative Inventory. Change it only if the business accepts negative stock for this item, such as backflushed components. - Repost after correcting the document, then run Adjust Cost - Item Entries if the correction changed costs. ## Sections ### Where the rule is defined **Body:** Prevent Negative Inventory exists in two places. In Inventory Setup it sets the default for every item. On the Item card (Replenishment or Posting fast tab depending on version) it can be set to Yes, No or Default, which lets you allow negative stock for a handful of items such as consumables or phantom-like components while keeping the global rule on. When the rule applies, the posting codeunits check remaining quantity on the item ledger for the posting combination and stop the post if the result would be below zero. The check includes the variant and location on the line, which is why a quantity that looks fine on the item card total still fails: the stock is at MAIN and the line says EAST. The check runs at posting, not when you enter the line, so a user can build a whole shipment and only meet the error on Post. Reservation and availability FactBoxes show a warning earlier, but they are advisory. ### The usual hidden causes **Body:** Location mismatch is the top one. Sales lines default the location from the customer or the document header, and warehouse employees often receive into one location code and ship from another. Run Item Availability by Location from the item card to see all balances in one view. Variant mismatch is second. An item with variants carries stock per variant, and a blank variant is a different bucket from variant RED. Lines created from copy-document functions or imports often lose the variant. Date order is third. Business Central is applying inventory by posting date, so a shipment dated the 3rd cannot consume a receipt dated the 5th. This often appears right after month-end when receipts were posted late and shipments were posted on their true dates. Finally, production consumption raises it too. A released production order posts consumption of components. If the component is short at the order's location, the consumption journal fails with the same message. Check the bin or location code on the production order component line. **Code:** On-premises SQL to see open balances by location and variant (replace CRONUS with your company): SELECT [Location Code], [Variant Code], SUM([Remaining Quantity]) AS OnHand FROM [CRONUS$Item Ledger Entry] WHERE [Item No_] = '1000' AND [Open] = 1 GROUP BY [Location Code], [Variant Code] ### When allowing negative inventory is reasonable **Body:** Some operations legitimately issue before they receive: backflushed raw materials where receipts are booked in a batch each shift, or items drawn on a consignment basis. Setting Prevent Negative Inventory to No on those items avoids blocking the floor, but it shifts the control to reporting. If you allow it, build a daily check on negative remaining quantity so the shortage is caught and fixed. Costing also suffers: negative stock means cost is applied later when the receipt arrives, so values change after Adjust Cost runs, and financial reports can move retroactively. For most finished goods and purchased items, leave the rule on. It is the only thing that forces a stock error to surface at the moment it happens. ## Pitfalls - Looking only at the Inventory total on the item card instead of the location and variant balance the line actually needs. - Turning off Prevent Negative Inventory globally to get one shipment out, then losing the control for every item. - Posting a shipment dated before the receipt it depends on, which shows negative at the earlier date. - Ignoring unposted receipts or production output that would satisfy the demand. - Not running Adjust Cost after posting against negative stock, leaving cost values provisional. ## Ai Angle This is a lookup problem across item ledger, location and variant, which is where a grounded assistant helps. Asked why a line is short, ERPray can query open item ledger entries for the exact item, location and variant, list unposted receipts and production output that would cover it, and show the SQL or API query it used. It is read-only, so any posting or setup change remains a user action. ## Faq ### Why does the item card show stock but posting still fails? **Answer:** The check is per item, variant and location. The item card shows an overall figure, but the line may name a different location or an empty variant. Open Item Availability by Location, or filter Item Ledger Entries on the line's location and variant, to see the balance that actually applies. ### Where do I allow negative inventory in Business Central? **Answer:** Use Inventory Setup for the company default and the Prevent Negative Inventory field on the Item card to override it per item. Setting it to No on the item lets that item go negative while the global rule stays on for everything else. ### Does the posting date affect this error? **Answer:** Yes. Business Central applies stock by posting date, so an issue dated before the matching receipt appears to have no stock on that date. Post the receipt with its true date, or move the shipment's posting date after the receipt, and the error clears. ### Can this happen with production consumption? **Answer:** Yes. Posting consumption from a released production order consumes component stock at the order's location. If the component is short there, or in the wrong bin, the consumption journal raises the same error. Fix the location on the component line or move stock first. ## Search terms business central insufficient quantity on inventory, business central prevent negative inventory, bc item ledger entry remaining quantity, business central negative inventory, business central cannot ship insufficient inventory, bc item availability by location, business central consumption journal error, adjust cost item entries --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json