On-hand inventory at landed cost in Sage Intacct. The working-capital line on the balance sheet.
At a glance
Total on-hand inventory valued at the costing method configured on the Sage Intacct Inventory Item record (Average, Standard, FIFO, or LIFO depending on the Inventory Control or Inventory Management module the merchant has licensed). The working-capital line on the consolidated Balance Sheet across every entity in the Multi-Entity Console, with each unit dimension-tagged so the same total can be cut by Department, Location, Project, Item, Class, Customer, or Vendor without re-querying.
Calculation
Calculated automatically from your Sage data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A US B2B distributor running Sage Intacct Multi-Entity Console with two regional entities (East Coast Distribution Inc, USD; West Coast Distribution Inc, USD) and a small Canadian fulfillment sub (CAD). Annual revenue ~$60M, mostly Net-30 wholesale through BigCommerce B2B and Adobe Commerce wholesale portal. Snapshot 14 Apr 26. Reporting currency USD. Costing method: Average across both US entities, FIFO on the lot-tracked Canadian sub.
Five things to notice:
- **60M revenue base it represents roughly 6 months of stock at full sell-through, materially above the 3 to 4 months a healthy mid-market distributor targets. The first conversation with the Implementation Partner is whether the costing method is producing a clean read or whether Standard-costing variances on the West Coast entity are bloating the headline; on this account the East Coast Average-cost basis is closer to economic reality. The second conversation is where the 6-month buffer came from. On most accounts it is a 2024-2025 supply-chain build that no merchandiser has unwound; the Controller cuts the same number by
Item.LastReceiptDateagainst the Inventory Aging card and the picture sharpens. - The Location dimension is the killer cut on Intacct. Five Warehouses across three entities, each surfaced as its own Location dimension on the GL detail. The same $30.33M can be re-cut in one click: by Department (East Coast Sales, West Coast Sales, Canadian Operations), by Project (capital-asset projects that have inventory carried as project stock), or by Class (brand or business-unit segmentation). NetSuite’s Class / Department / Location segmentation supports this conceptually but Intacct’s eight first-class dimensions tag every transaction line by default and query without saved-search engineering. For a Finance Controller who lives in Intacct daily, this is the headline difference; a Vortex IQ Implementation Partner conversation usually centres on how much of the dimension model the merchant has built out.
- In-transit at $1.18M is goods in containers en route from Asia. Stock received against a PO under Intacct’s Goods in Transit workflow but not yet posted into a physical Warehouse. The dollars sit on the consolidated Balance Sheet under Inventory but are not sellable yet. Most distribution accounts run a 4 to 8% in-transit ratio depending on container lead times; this account at 3.9% is on the leaner side. The number matters for treasury planning because in-transit dollars are committed cash that has not yet generated a Sales Order line.
- The East/West split (60/40 by dollar value) matches the geographic sales mix. When this ratio drifts, fulfilment lag follows: a 70/30 inventory split against a 50/50 sales split means West Coast customers are getting longer ship times because the East Coast warehouse is shipping into West Coast territory. Pair this card with the Open Order Value cut by Location dimension to confirm. On this account the Operations Manager has been chasing a quiet 2-week ship-time creep on West Coast B2B accounts; the inventory split-vs-demand split makes the cause visible.
- **The Canadian sub’s FIFO costing on 30.33M total because the GL aggregates dollar-cost regardless of underlying lot detail.
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in Sage Intacct: The native Sage Intacct views to run side by side with this card:Reports → Inventory Control → Inventory Valuation Summary (the canonical valuation report at intacct.com) Reports → Inventory Control → Item Stock Status (real-time on-hand by Warehouse / Location) Reports → Financial → Balance Sheet (Inventory line, dimension-aware roll-up) Reports → Financial → Trial Balance with Dimensions (per-account, dimension-pivoted) Interactive Custom Report (ICR) built on the Inventory data source filtered to stocked items, summed onThe Inventory Valuation Summary is the gold-standard tie-out at intacct.com. The Balance Sheet Inventory line should match this card to within rounding when the entity scope and snapshot date are aligned. Most Implementation Partners build a saved ICR called something like “Inventory Tie-out, Consolidated” that reproduces the card’s logic against Intacct’s GL Detail; once built, it becomes the monthly month-end reconciliation report. Common reconciliation pitfalls:QuantityOnHand × UnitCost, pivoted by Location and Department dimensions Smart EventINVTOTALfor live on-hand snapshots (Inventory Control module only)
- Costing method mid-period change: if the merchant flips an item’s
COSTMETHODfrom Standard to Average mid-period, the card recomputes from the new basis at the next snapshot, while a historical Inventory Valuation Summary used the old basis. The headline can move 2 to 5% on a single item that bridges the change. - Per-entity Currency Configuration: Multi-Entity Console accounts: each entity’s inventory translates to reporting currency at the entity’s configured FX cadence (transaction-date, period-end, or period-average). A Balance Sheet run at the Top Level entity uses period-end FX, the card uses current-day FX; differences typically under 2%.
- In-transit inclusion: the Inventory Valuation Summary by default includes Goods in Transit if the merchant uses the Inventory Control Goods-in-Transit feature; the Balance Sheet inventory line includes them too. If the merchant uses Order Entry’s Inter-Entity Transfer workflow without Goods in Transit, the in-transit dollars sit in a clearing account and the card excludes them.
Cross-connector reconciliation:
Known limitations / merchant FAQs
What’s a healthy inventory ratio? Wholesale distribution: 3 to 4 months of COGS. Apparel and fashion: 3 to 5 months. Industrial distribution: 4 to 8 months (longer cycles are normal). Food and beverage non-perishable: 1 to 2 months. SaaS and services-led businesses on Intacct: typically less than $500K of inventory total because the product is intangible, so this card is not load-bearing. Compare to your own 12-month rolling baseline first; absolute ratios mislead across categories. Average vs FIFO vs Standard, which is “right”? Whatever your accounting policy says. Sage Intacct supports all four (Average, Standard, FIFO, LIFO). The card uses whatever each Inventory Item record’sCOSTMETHOD field dictates. Average is the most common across mid-market commerce on Intacct; FIFO is preferred for lot-tracked perishables and regulated goods; Standard is common for distribution where a periodic standard-cost roll is part of the close cadence. The Implementation Partner usually picked the method on day one based on tax and audit policy.
Sage Intacct vs NetSuite on this metric, what’s different?
Arithmetic is identical: on-hand quantity times unit cost, summed across locations and entities. Where Intacct shines is the dimensional cut: the same headline can be sliced by Department, Location, Project, Item, Class, Customer, Vendor, or Employee in one click because every inventory transaction is dimension-tagged at posting. NetSuite has Class / Department / Location segmentation, but Intacct’s eight first-class dimensions tag every line by default and query without saved-search engineering. For a Finance team that lives in dimensions, this is the daily difference. For pure stock-on-hand reporting the answer is identical.
Sage Intacct vs Sage 50 / 100 / 200 / X3 on this metric?
Different products. This connector targets Sage Intacct only (US mid-market cloud financials with dimensional accounting). Sage 50 and Sage 100 are SMB desktop products with a much simpler costing model, no Multi-Entity Console, and no first-class dimensions. Sage 200 is a UK / EU SMB product. Sage X3 is a different mid-market ERP with deeper manufacturing and process-industry support. The arithmetic is conceptually similar across all of them but the API, dimensions, and reconciliation paths differ. If you are running Sage 50 / 100 / 200 / X3, reach out about connector availability.
Multi-Entity Console: how does FX work on this card?
Each entity holds its inventory in its own base currency. The consolidation translates to the Top Level reporting currency (typically USD on a US-headquartered account) at the configured cadence per entity. The Currency Configuration in Intacct sets cadence per entity: transaction-date for goods movement, period-end for Balance Sheet revaluation, period-average for Income Statement translation. Inventory uses period-end by default; the card snapshots at current-day FX which is closest to economic reality. Differences typically under 2% in normal market conditions, larger if FX has moved sharply between the snapshot day and the most recent period-end revaluation.
REST vs XML API, does it matter for this card?
No effect on the number. Sage Intacct exposes inventory through both APIs. The XML API (the long-standing Smart Events and List queries) is the workhorse for bulk inventory reads and runs faster on large item catalogues; the REST API is preferred for single-item reads and webhooks. Vortex IQ’s connector uses XML for the bulk valuation read (typically a single query against INVENTORY_TOTAL) and REST for incremental refresh on item changes. Freshness on the card is typically 5 to 15 minutes from the most recent Intacct transaction.
Why is Total Inventory rising while sales are flat?
Three usual causes on a US distribution account: (1) over-ordering from suppliers, often a 2024-2025 supply-chain build that nobody has unwound; (2) demand drop on previously-fast SKUs, which surfaces on Inventory Aging as a bulge in the 91-180 bucket; (3) longer lead times causing safety stock to balloon, particularly on overseas Asian sources where 90-day lead times have become structural. Drill via Inventory Aging and Dead Stock Value.
Manufacturing WIP, included?
Excluded by default. Sage Intacct does not have a native manufacturing module; merchants running production carry WIP through a third-party connector (MRPeasy, Katana, Fishbowl) or a custom Inventory Control workflow. The card includes whatever Intacct’s Inventory Item records track as on-hand at any Location. WIP held outside Intacct (inside the manufacturing system) does not appear in this card; the merchant runs a separate WIP report there.
Lot and serial-numbered items, do they read differently?
Yes if the costing method is FIFO or LIFO. Each lot or serial carries its receipt cost as a separate cost layer; the card aggregates to the dollar total. For Average-cost items the lot detail is invisible at the card level. Lot-level views are valuable for perishables, pharma, food, and regulated cosmetics where lot traceability is a compliance requirement; the card surfaces the headline, the lot detail lives in Intacct’s Inventory Item record drill-down.
Stock revaluation impact?
Intacct’s Inventory Adjustment workflow can revalue stock through the Inventory Control module’s price-update or recosting features. After a revaluation the card respects the new basis; the historical period’s value (locked in a closed period) stays at the original basis. Auditors expect to see revaluation entries during year-end review; the card surfaces the post-revaluation total and the Margin Erosion Alerts card flags any per-SKU margin movements that revaluation caused.
Multi-Entity Console: per-entity vs consolidated view, which to use?
Both. The consolidated Top Level view is the boardroom and audit number. Per-entity views are operational: a Controller managing the West Coast entity wants to see West Coast inventory separately, the Operations Manager managing the Canadian sub wants the Canadian-only cut. The card respects the dashboard entity filter; the same query produces both views and the Implementation Partner usually pins both as separate Nerve Centre tabs.
Vendor-managed inventory (VMI), does it count?
Depends on title. If the supplier holds title until consumption (true VMI), the stock is not on the merchant’s Balance Sheet and not in this card; Intacct typically tracks it on a memo Location flagged “VMI, not owned”. If the merchant holds title from receipt (consigned-in), the stock is on-hand and the card includes it. Confirm with the auditor and the Implementation Partner; the field map respects whichever convention is configured.
Implementation Partner role on this metric?
Most Sage Intacct merchants are paired with an Intacct-certified Implementation Partner (often a regional accounting firm or VAR). The Partner typically owns the Inventory Control module setup, the Chart of Accounts mapping for the 1300-1399 Inventory range, the dimension structure on Inventory Items, and the saved ICR library. If this card returns a different number from the Partner’s monthly board pack, the cause is almost always (1) a costing method change captured by one side and not the other, (2) a Goods-in-Transit configuration discrepancy, or (3) a per-entity FX cadence mismatch. Vortex IQ’s field map is the place to align; the Partner is the right person to invite into the conversation.