Inventory modelling in D365: a new discipline for Unit4 organisations

Unit4's lightweight stock model versus D365's full inventory framework — storage and tracking dimensions, valuation methods, inventory close, and the irreversible decisions that must be made correctly on day one.

What you will be able to do

Introduction

Unit4 is finance-first and inventory-light. This is not a limitation — it is an accurate reflection of the customer base it serves. Public-sector bodies, universities and professional-services firms do not run warehouses; they manage time, expenses and contracted services.

What Unit4 actually provides

Unit4's procurement and inventory capabilities cover: Requisition, Purchase Order, Goods Receipt (lightweighted), Supplier Invoice, match-and-approve, and Payment. The goods receipt in Unit4 posts an accrued-not-invoiced balance per PO line; it does not maintain a separate GR/IR clearing account lifecycle.

The D365 inventory hierarchy: site, warehouse and location

D365 structures physical inventory through a three-level hierarchy (four levels if pallets are tracked):

Storage and tracking dimension groups

Every released product has two dimension groups that control how inventory is tracked:

Inventory model groups and costing methods

The Item model group is assigned per released product and governs: The inventory model (costing method): FIFO, LIFO, weighted average, moving average, or standard cost. Whether the product is stocked (on-hand quantity tracked) or non-stocked (cost posts directly; no on-hand). Whether negative inventory is permitted.

Basic warehousing versus WMS

Basic warehousing uses the standard inventory transaction model with optional location tracking. Pick and pack are managed through sales order or purchase order journals, manually or semi-automated. Counting journals drive cycle counting. No mobile device integration. No work templates or location directives.

Knowledge check

Summary

Inventory modelling is, for most Unit4 organisations, a new discipline rather than a migration. The concepts exist in Unit4 but are rarely deep; in D365 they are structured, typed and consequential.