Companies, Sites, Warehouses and the operating-model decision
How Epicor's Company / Site (Plant) / Warehouse / Bin hierarchy maps onto D365 legal entities, operational sites, warehouses and warehouse locations — and why the Site-level decision shapes everything downstream.
What you will be able to do
Map Epicor Company to D365 legal entity and explain why the mapping is 1:1 with caveats for consolidation-only companies
Evaluate when an Epicor Site becomes a D365 site, a financial dimension, or both
Describe multi-company Epicor versus D365 cross-company data sharing and intercompany trade
Explain the fiscal calendar and currency setup consequences at legal-entity level
Produce a defensible organisational-model design table for a multi-site Epicor estate
Introduction
The Conceptual Foundations chapter established that an Epicor Kinetic migration is dominated by the customisation surface, GL segment compression, multi-book redesign, and MOM split — not by the standard functional footprint.
Company to legal entity — the 1:1 anchor
The chart of accounts (segmented GL structure) The fiscal calendar and period definitions The base (accounting) currency The Books (multi-book policy sets) Security group assignments and menu access
The Site decision — operational boundary, financial dimension, or both
An Epicor Site (also called a Plant) is a manufacturing and inventory location within a Company. Inventory is tracked at part-by-site-by-warehouse-by-bin granularity. A Site is operational, not statutory — it does not own a chart of accounts or file statutory returns.
Warehouses and Bins
Epicor Warehouses sit within a Site and hold inventory. A Warehouse subdivides into Bins — the lowest-level physical storage location.
Multi-company data sharing and intercompany trade
Epicor multi-company implementations can share reference data (payment terms, delivery modes, tax types) across companies. In D365, the equivalent mechanism is cross-company data sharing policies — configurable rules that share specific tables across designated legal entities.
Fiscal calendar and currency at entity level
An Epicor fiscal calendar defines the reporting periods for a Company — standard 12-month, 4-4-5, 13-period, or custom definitions. D365 maps this directly: a fiscal calendar (FiscalCalendar) with period definitions is assigned to the ledger on each legal entity.
Producing the organisational-model design table
Before Wave 1 configuration begins, the programme must produce a signed-off design table mapping every Epicor organisational node to its D365 target. A representative format:
Knowledge check
Summary
The Epicor organisational model maps to D365 with high structural alignment at the Company and Warehouse levels. The critical decision sits at the Site level — where the programme must determine whether each Site carries financial-reporting weight that requires a financial dimension, or whether it is purely operational.