Finance asks a version of the same question every month. The stock valuation report says one number, the inventory account in the general ledger says another, and nobody can explain the difference without a week of spreadsheet work. The gap is rarely random — it is the visible symptom of how stock movements were valued and how they were posted.

This page walks through the mechanics: how Sage X3 assigns value to stock, how that value reaches the ledger, what commonly breaks the link between them, and a reconciliation sequence you can run at any period end. Table and parameter names appear where they help a technical reader locate something; they are reference points for review, never an invitation to edit data directly.

Talk to a Senior Sage X3 Consultant

What the problem looks like

The stock valuation report does not equal the inventory GL balance, and the gap grows each month
FIFO cost layers no longer line up with the on-hand quantity for a product-site
Movements recorded with quantity but no value, or value with no quantity
Work-in-process value that never clears after a work order is closed
Stock movements sitting unposted after the stock accounting interface has run
Auditors asking how inventory was valued at year end, and the answer taking days to assemble

How valuation reaches the general ledger

Sage X3 keeps two related records for every piece of stock activity: a quantity and a value. Understanding where each one is created explains almost every reconciliation difference.

Every movement is valued in the stock journal

Each stock movement is written to the stock journal with a quantity and a value derived from the valuation method set on that product-site. The journal is the historical record of how value entered and left stock.

The stock accounting interface posts value to accounting

Movements reach the ledger through the stock accounting interface, run periodically or automatically depending on configuration. It uses the movement's automatic journal along with accounting codes on the product and site, and the movement group or type, to select accounts.

Layer methods and single-cost methods behave differently

FIFO, LIFO, and lot cost maintain cost layers (held in the stock cost tables, STOCOST) that must stay aligned with the physical stock lines. Average and standard maintain a single cost per product-site instead of layers.

Standard-valued products post variances

For products valued at standard, purchase and production differences post as variances rather than changing the value carried in stock. Finance sees the difference in the variance accounts, not in the inventory balance.

WIP sits on open work orders

Work in process is carried on work orders in progress and released at production receipt and close. Incomplete closes leave value stranded in WIP, which shows up as a difference that no stock line explains.

Why the stock report and the GL drift apart

Movements not yet posted by the stock accounting interface, or posted into a period different from the movement date
Manual journal entries booked directly against the inventory account
Accounting code mapping that routes some movement types — often a custom miscellaneous movement — to accounts outside inventory
A valuation method changed on a product-site that still held stock on hand
FIFO layer desynchronization caused by negative stock, interrupted transactions, or direct data changes, which later surfaces as WIP finalization or issue errors
Physical count adjustments posted at values nobody reviewed before validation
Custom transactions or integrations writing stock lines without producing the corresponding accounting entries

Each cause leaves a different fingerprint, which is why reconciling by movement type is far more productive than reconciling product by product.

A reconciliation sequence that works

1. Fix the cut-off
Pick one period end and extract two datasets at exactly that date: stock valuation by product-site, and the inventory GL balance by site and account.
2. Confirm everything is posted
List stock movements through that date that have not been posted to accounting. Unposted movements are the single most common explanation and the easiest to rule out.
3. Compare by movement type, not by product
Total the stock journal by movement type and group, and compare those totals to the GL postings by account for the period. Differences isolate which movement types have mapping problems.
4. Review the transaction history on the ledger side
Look for manual journals against inventory accounts. Any entry that did not originate from a stock movement will never appear in the valuation report.
5. Validate costing on layer-based products
For FIFO products throwing errors, compare cost layers against on-hand quantity per product-site to find the desynchronized records rather than assuming the whole product family is affected.
6. Test the correction away from production
Prove out configuration changes and any valuation correction in a non-production folder, including the resulting accounting entries, before touching the live environment.
7. Correct forward, adjust history deliberately
Fix the configuration so future movements post correctly, then book a documented adjustment for the historical difference rather than rewriting history.
8. Monitor so it does not return
Put a recurring query in place that compares stock value to the GL balance by site each period, so the next divergence is caught in days rather than quarters.

When this needs a senior consultant

The gap has persisted across several periods and no one can attribute it
FIFO layers are corrupt and issues or WIP finalization are now failing
Custom movement types or integrations are writing stock activity
A year-end audit deadline is driving the timeline
The incumbent partner proposes a mass revaluation without identifying a root cause

PRH approaches valuation gaps as a diagnostic problem first. We run targeted queries against the stock cost and product-site tables to find where value and quantity diverged, correct through supported functions rather than mass batch operations against live data, and leave a weekly monitoring query behind so the reconciliation stays clean after we step back. A mass revaluation that has not been explained tends to reappear next quarter.

Inventory valuation questions

Why doesn't my Sage X3 stock valuation match the GL?

In most cases: movements not yet posted to accounting, manual journals booked directly against the inventory account, or accounting code mapping sending some movement types to other accounts. Reconciling by movement type will usually identify which of the three applies.

What inventory valuation methods does Sage X3 support?

Average unit cost, FIFO, LIFO, standard cost, revised standard cost, lot cost, and last cost. The method is set per product-site, so the same product can be valued differently at different sites.

Can I change the valuation method of a product in Sage X3?

Yes, but with stock on hand it should be treated as a controlled cutover with a planned accounting impact — not a field change made during a normal working day.

What causes FIFO errors in Sage X3?

Cost layers falling out of step with on-hand quantity, typically after negative stock has been allowed, a transaction was interrupted, or data was changed outside the application.

How does Sage X3 post stock movements to the GL?

Through the stock accounting interface, which uses automatic journals together with the accounting codes on the product and site to determine the accounts. Behavior depends on how that configuration was set during implementation.

How do I value WIP in Sage X3?

Work in process is carried on open work orders; value is released at production receipt and at close. Orders still open at period end represent the WIP balance, which is why incomplete closes distort the period.

Sage X3 Inventory Valuation and Stock-to-GL Reconciliation