NetSuite inventory valuation report: why it won't tie to the GL

Every controller with inventory has had this month. The NetSuite inventory valuation report says $4,182,640. The inventory asset account on the trial balance says $4,206,915. The difference is $24,275, nobody knows where it came from, and close is tomorrow. The good news is that the gap is almost always one of about seven things, and most of them are structural rather than a mistake.

What the report actually computes

NetSuite's Inventory/Items report category holds two versions: Inventory Valuation Summary, one row per item, and Inventory Valuation Detail, which breaks the value down further. Both compute the same thing — on-hand quantity as at a date, multiplied by the cost the item's costing method says applies.

Inventory valuation

The balance-sheet value of stock you own and haven't sold yet. Quantity is a physical fact; cost is an accounting policy. Two companies holding identical stock can carry materially different inventory values, entirely legitimately, because they chose different costing methods.

Why the report and the GL disagree

Work these in order. In most accounts the first three explain more than 90% of the variance.

Point 7 deserves emphasis because it undermines trust in the whole report. NetSuite recalculates costing when transactions are entered out of chronological order — a receipt dated last Tuesday, entered today, reprices the issues that happened in between. That recalculation is not instantaneous. A valuation report run mid-close can legitimately differ from the same report run the next morning with nothing new dated in the period. Print it, date-stamp it, and file the printout.

Getting quantity and cost yourself

For a working list rather than a report, an Item saved search gives you on-hand quantity, average cost and — with the inventory-location join added — the same numbers broken out per location. Two things make it much more useful:

• Add a value formula. A numeric formula column multiplying on-hand quantity by cost gives you a value column you can sort, which the canned report's summary layout makes awkward. Treat it as an approximation for prioritisation, not a substitute for valuation.
• Add last-activity dates. On-hand quantity next to "last received" and "last sold" turns a valuation list into a slow-moving-stock list. That is usually the question behind the question, and it is where the write-down conversation starts.

The reconciliation query

Do not try to recompute layer-level valuation in SuiteQL. It is possible, it is slow, and it will disagree with NetSuite's own costing engine in edge cases you won't find until an auditor does. What SuiteQL is genuinely good for here is the ledger side, per item, which is exactly what the reconciliation needs:

SELECT
  BUILTIN.DF(tl.item)                          AS item,
  BUILTIN.DF(tal.account)                      AS asset_account,
  ROUND(SUM(tal.debit) - SUM(tal.credit), 2)   AS gl_value
FROM transactionaccountingline tal
JOIN transactionline tl ON tl.transaction = tal.transaction
                       AND tl.id          = tal.transactionline
JOIN transaction t      ON t.id = tal.transaction
JOIN account a          ON a.id = tal.account
WHERE a.accttype  = 'InvtAsset'
  AND tal.posting = 'T'
  AND t.trandate <= TO_DATE('2026-06-30', 'YYYY-MM-DD')
GROUP BY BUILTIN.DF(tl.item), BUILTIN.DF(tal.account)
HAVING ROUND(SUM(tal.debit) - SUM(tal.credit), 2) <> 0
ORDER BY gl_value DESC

Run that, run the valuation report, and put the two lists side by side keyed on item. The rows that don't match are the whole investigation, and there are usually fewer than twenty of them. Rows with a blank item and a real balance are point 2 from the table above; you have found them in about ninety seconds rather than by scrolling a general ledger. The SuiteQL formatter is handy if you inherit this query pasted into a wiki page as one long line.

Reading the valuation, not just producing it

Once the number ties, it is worth thirty more seconds of thought, because inventory value is the most expensive line on a distributor's balance sheet.

• Value concentration. Sort descending by value and look at the top 30 items. If 20 items are 70% of value, your cycle counting, buffer policy and review cadence should all be shaped around those 20 — not spread evenly across 4,000 SKUs.
• Value with no movement. Items with real value and no issue in 180 days are the write-down candidates. Being able to name them before the auditor does is the difference between a provision and a restatement.
• What holding it costs. Capital, storage, insurance, obsolescence and shrink typically total 18–28% of inventory value per year for mid-market distributors, which means $4.2M of stock costs real money to hold. The inventory carrying cost calculator breaks that into its components.
• Whether valuation is complete. If freight, duty and brokerage aren't in your item costs, your inventory is understated and your margins are overstated by the same amount. Landed cost: what to include covers the allocation methods, and inventory turnover: how to read it explains why turns move when costing changes even though nothing physical did.

Asking instead of building

Two reports, two queries, a keyed comparison, and a judgement about which differences are structural. That is a genuine skill and it is also a recurring Tuesday. Ask ERPray "inventory value by item at 30 June versus the inventory asset accounts, show me only the items that don't match" and you get the comparison computed live from your own account, with the SuiteQL printed underneath so the costing assumptions are visible rather than implied. Read-only by default — nothing in the ledger moves.