xMatix Inventory

xMatix Inventory tracks what stock you hold, where it is, and what it is worth. Its backbone is the inventory ledger: every movement — a receipt, a shipment, a transfer, an adjustment — is recorded as a posted entry, and on-hand stock is the running position those entries have moved rather than a number anyone types. On top of the ledger sit branch-to-branch transfers with a real in-transit state, stock adjustments, lot-level tracking, a perpetual costing engine that values stock under the method your accounting policy chooses, and period balances that roll it all up for comparison. This section explains each piece and the screens where you work with it.

Where the screens live

Inventory work happens in the Inventory app. Its navigation bar carries the documents you create and the statements you read:

Two lists you will use are not on the navigation bar: Item Lots (open from a lot link on a document or ledger entry, from search, or through a stock figure's Item lot details drill) and Item Inventory Attributes (the per-branch classification and replenishment rows, on the item's Inventory tab or through the app launcher search). Accounting books and valuation policies — the configuration that decides how stock is valued — belong to the Finance Setup app, and the read-only inventory ledger settings live under Setup → Feature Hub → Inventory. Both are covered in the configuration reference.

What this section covers

The pages are ordered so that each builds on the ones before it:

• The inventory ledger — the concept everything else rests on: every movement is a posted entry, corrections post reversals, and the Inventory Stock page is where you read balances.
• Stock balances — the stock record behind every availability check: one per company, branch, item, SKU and location, its quantity buckets, and how Available, In Hand and Quantity Projected are calculated.
• Transferring stock between branches — the two-document transfer: outward release, the in-transit state, inward receive and posting, the selective variants and the single-step alternative.
• Adjusting stock — correcting on-hand quantities with an adjustment document, the reason types, and when an adjustment is the right tool versus a cycle count.
• Item lots and lot types — batch- and serial-level tracking: what a lot records, which fields the platform maintains, and how lots follow stock through movements.
• Item lot types — commercial grades of an item (saleable, sample, promo): creating them, every field, and how they steer pricing, tax, schemes and lot allocation.
• Inventory valuation and costing — perpetual costing from the ledger, cost layers and consumptions, accounting books, valuation policies, the Inventory Valuation page and the engine's current limits.
• Inventory valuation policies — for administrators: choose the costing method per book, company, branch, business unit, item group or item, and what a policy save checks.
• Landed cost vouchers — recording freight, duty and other charges against received items, why a voucher never posts or changes stock value, and how to put those charges into stock cost instead.
• Inventory NRV assessments — recording a lower-of-cost-and-net-realisable-value write-down or reversal for an item, how the Valuation Statement applies it, and the journal you post yourself.
• Inventory period balances — how the ledger rolls up into per-period opening, inward, outward and closing figures in quantity and value.
• Items (the item master) — creating and maintaining items: the required fields, the stock and behaviour flags, units of measure, packages, and why a new item starts inactive.
• Item units of measure — alternate units such as boxes and cases: adding them, conversion ratios, the two unit slots on a line, rounding, and the "UOM is not defined" error.
• SKUs (item variants) — the variants of an item: adding them, SKU Required, how stock, lines and pricing rules follow the SKU.
• Item aliases — another name or code for an item (a customer's part number, a retailer's nickname): creating and scoping them, and what lines fill in and check when they use one.
• Item alternates — substitute and superseded items: setting them up, how a superseded item is replaced on new lines, and the Alternate Items popup and Item 360 panel.
• Item relations (related items) — the parts and labour allowed with a parent item, and how they limit the lines a service order for an asset accepts.
• Packages and item components — the contents of a package item: which components are added to document lines, how their quantities scale, bundled prices and mandatory parts.
• Item features (option groups) — the named groups a package's components are listed under in the product configurator, and which of their settings have an effect.
• Item inventory attributes — the per-item planning rows: order limits checked on purchase-order lines, the stock levels and lead times automatic ordering reads, which row each process uses, and every save rule.
• Item classifications — the ABC and FSN categories, where they are stored, and where auto-ordering, cycle counting and reports read them.
• Inventory ledger settings (posting rules) — for administrators: the read-only rules that decide which ledger entry each document line writes and which stock buckets it moves, and how to trace a posting back to its rule.
• Inventory configuration reference — for administrators: the inventory ledger settings, the item-master stock flags, and the valuation configuration.
• Troubleshooting inventory — what to check when stock or valuation looks wrong, and what a closed period blocks.

Three rules that hold everywhere

• Nothing moves stock until it is posted. Creating an adjustment, a transfer or their lines records intent only. Stock changes when the document's action runs (Post Inventory, Release Outward), and the reliable proof that a line reached the ledger is its Inventory Ledger reference — not a status label.
• Posted entries are never edited. Correcting a posted line makes the ledger add negated reversal entries and fresh entries for the new values; the originals stay. Read pairs of opposite entries as history, not as errors.
• A movement that would take a stock counter negative is rejected. The posting fails with an Insufficient stock message naming the counter, and nothing is written. The fix is always on the source document — quantity, lot or location — never on the ledger.

Who can do what

Access to the Inventory app and its screens is granted through the user's security profile and the app's page permissions, like every other xMatix app. Posting, release and receive are entity actions, so a profile can allow a user to create and edit documents without letting them post. Accounting books and valuation policies sit in Finance Setup and normally belong to finance administrators. If a user cannot see a screen described here, start with why a user can't see something.

Where Inventory ends and neighboring modules begin

Inventory owns stock truth: the ledger, transfers, adjustments, lots and valuation. Warehouse operations that act on that stock — cycle counting, picking, putaway, receiving at the bins and fulfilment execution — are covered in the warehouse documentation, and replenishment — reorder rules and automatic purchase suggestions — in the procurement documentation. Goods receipts and sales shipments post their stock effects through the same inventory ledger described here, so the reading skills from this section apply everywhere.

Related topics

• xMatix Inventory product overview
• xMatix Warehouse documentation
• xMatix Procurement
• xMatix documentation home