Your Odoo stock valuation does not match - here is why

You went live on Odoo, ran the Inventory Valuation report at month end, and the total does not match the stock figure on your balance sheet. Or it does not match the physical count your warehouse just finished. Either way, your accountant is not signing off, and you cannot close the month. This is one of the most common post-go-live issues we are called in to fix, and the good news is that it is rarely data corruption. It is almost always one of five specific, well-understood causes - and each has a clean fix.

This guide walks through how to identify which mismatch you actually have, the five usual causes in order of how often we see them on Indian and UAE deployments, and the exact reconciliation step for each. It assumes Odoo's real-time (perpetual) inventory valuation, which is the default for anyone running Anglo-Saxon accounting.

First, name the mismatch precisely

"The valuation is wrong" is three different problems. Before you touch anything, identify which two numbers disagree, because that pair tells you where to look:

• Valuation report vs general ledger. The Inventory Valuation report does not equal the balance of your stock accounts. This is an accounting wiring problem - interim accounts, manual journals, or a costing method change.
• Valuation report vs physical count. Odoo's quantity-times-cost does not match what is on the shelf. This is a quantity problem (uncounted moves, negative stock) or a unit-cost problem (zero-cost opening balances).
• Two valuation snapshots that should match but do not. The valuation at a past date no longer reconciles - usually a backdated move that recomputed cost after the fact.

Write down the two numbers and the gap in rupees or dirhams. Most teams skip this and start re-importing data, which makes a fixable accounting gap into a real one.

The five usual causes, in order

1. The wrong costing method, or a method changed mid-stream

Odoo offers three costing methods per product category: Standard Price, First In First Out (FIFO), and Average Cost (AVCO). If a category was left on Standard Price but you import goods at varying real costs, the valuation drifts away from what you actually paid. Worse, if someone switched a category from Standard to AVCO after stock already existed, Odoo revalues on the fly and the historical numbers move. The fix is to decide the right method per category once, set it deliberately, and post a one-time revaluation so the on-hand value reflects real cost going forward. If you are unsure which method fits, our breakdown of Odoo inventory valuation methods shows when FIFO beats AVCO for an Indian SME and when it does not.

2. Opening stock loaded at zero or wrong unit cost

This is the single most common cause we see at go-live. The migration loaded quantities correctly but the unit cost came in as zero, blank, or a rounded placeholder. Quantities match the physical count perfectly, yet the valuation is far too low because half your SKUs are valued at nothing. The fix is a stock revaluation that sets the correct unit cost on the affected products, posted as of the go-live date so the opening balance is right. Do not adjust quantities to compensate - that breaks the count to fix the value, and you end up with both wrong.

3. Manual adjustments that bypassed the valuation layer

When stock is corrected outside Odoo's inventory moves - a direct database edit, an imported quantity change, or a journal entry made straight to the stock account - the quantity and the value fall out of sync. Odoo's valuation is driven by stock moves; anything that changes stock without a move leaves the ledger and the report disagreeing. The fix is to stop all out-of-band corrections, then post proper inventory adjustments (which generate the matching valuation entries) to bring the two back in line.

4. Stock interim accounts left unreconciled (Anglo-Saxon accounting)

With real-time valuation, Odoo uses interim accounts - Stock Interim (Received) and Stock Interim (Delivered) - to hold value between a goods receipt and the vendor bill, or a delivery and the customer invoice. If bills or invoices are not posted, value gets stranded in these interim accounts and the stock account on the GL no longer matches the valuation report. The fix is to reconcile the interim accounts: post the missing bills and invoices so value flows out of interim and into the correct stock or expense account. A non-zero interim balance at month end is the tell.

5. Negative stock and backdated moves recomputing cost

If a product was allowed to go negative - a sale recorded before the receipt that supplied it - Odoo guesses a cost, then recomputes when the real receipt lands, and the historical valuation shifts retroactively. Backdated moves do the same thing. The fix is to prevent negative stock in the first place and re-sequence the affected moves in true date order so cost is calculated correctly. Our guide to preventing negative stock in Odoo covers the exact configuration that stops this at the source.

The reconciliation procedure that works

Work top-down, never by guessing. Run the Inventory Valuation report at the close date and the Trial Balance for the same date. Compare the report total to the stock account balance. If they differ, check the interim accounts for stranded value - that gap is cause 4. If the GL ties to the report but neither matches the physical count, the problem is quantity or unit cost - causes 2, 3, or 5. Only once you know which layer is wrong do you post a correction: a revaluation for cost, an inventory adjustment for quantity, or a reconciling journal for interim balances. Document each correcting entry with a reason so your auditor can follow it. This disciplined trace is what separates a clean fix from a month of chasing your own corrections - and it is exactly the kind of post-go-live stabilisation our Odoo support team runs every week.

Preventing it at the next go-live

Most valuation mismatches are designed in before go-live, not caused after. Three habits prevent almost all of them. First, load opening stock with real, verified unit costs - never zero, never a placeholder - and reconcile the imported valuation to your old system on day one. Second, lock the costing method per product category deliberately and do not change it once stock exists; if you must, plan the revaluation that comes with it. Third, disable negative stock from the start so cost is never guessed and recomputed. Getting these right during a properly scoped Odoo implementation is the difference between a clean first close and a month of reconciliation. If inventory accuracy is the core reason you moved to Odoo, our inventory management approach builds these controls in from the start.

FAQ

Why does my Odoo stock valuation not match my balance sheet?

The most common reason is value stranded in the Stock Interim accounts because vendor bills or customer invoices have not been posted, or a manual journal was made directly to the stock account without a matching stock move. Run the Inventory Valuation report and the Trial Balance for the same date, then check the interim account balances - that gap is usually the cause.

Why is my Odoo valuation low even though quantities are correct?

Your opening stock was almost certainly loaded at zero or a placeholder unit cost. The quantities match the physical count, but products valued at nothing pull the total down. Fix it with a stock revaluation that sets the correct unit cost as of the go-live date - do not change quantities to compensate.

Can I change the costing method after go-live in Odoo?

You can, but Odoo revalues existing stock when you do, so historical numbers will move. Decide the right method per category before stock exists if at all possible. If you must change it later, plan the one-time revaluation entry and document it for your auditor rather than letting the system silently shift past figures.

How do I stop negative stock from breaking my valuation?

Disable negative stock at the product or location level so a sale cannot be recorded before the receipt that supplies it. When stock goes negative, Odoo guesses a cost and recomputes it later, which moves your historical valuation retroactively. Prevent it at the source and re-sequence any affected moves in true date order.

The bottom line: a stock valuation mismatch is a tracing problem, not a re-implementation. Name which two numbers disagree, match the gap to one of the five causes, post a documented correction, and lock the configuration that caused it. Do that once and your month-end close stops being a fight with your own data.