Unit4 articles and charge codes to D365 product master and released products

How Unit4's lightweight article and charge-code model maps to D365's structured product master, and why the attribute-based data model does not carry across — D365 separates product identity, product dimensions and financial dimensions into three distinct mechanisms.

What you will be able to do

Introduction

Unit4's product and article model reflects the system's people-and-services orientation. Most Unit4 customers carry a modest article catalogue — physical goods for organisations that move some stock, and charge codes or service codes for the much larger population that bills for time, expenses and contracted services.

What Unit4 actually holds

An Article in Unit4 is a master record covering both physical goods and non-stocked service codes. It carries: article code, description, unit of measure, article group (the primary classification for GL posting), a valuation basis (FIFO or weighted average for stock items), a default cost and optionally a default sales price, and a…

The D365 product model: two levels and three dimension types

Product master (EcoResProduct) — the shared, cross-company definition of a product or service. Carries the product name, product type (item or service), product dimension group, and product attributes. Shared across all legal entities in the environment.

Article groups, item model groups and posting

The article group in Unit4 is the primary lever for GL posting: it determines which accounts a purchase receipt, a goods issue or a sales line posts to. The migration equivalent in D365 is a combination of the Item group (which drives inventory posting accounts) and the Item model group (which governs the inventory valuation method —…

Product categories and FlexiField partition

D365's product category hierarchy provides a structured taxonomy of what is being procured or sold — independent of which legal entity or which financial dimension. A typical professional-services category hierarchy covers: consultancy services, travel and expenses, software licences, hardware, and maintenance.

Knowledge check

Summary

Unit4's article and charge-code model is lean by design. Most Unit4 organisations arrive at D365 with a modest product catalogue, primarily service-type items. The migration is technically straightforward; the design work is in making the distinctions that Unit4 never required.