Segment compression and the financial dimension model

How to translate Epicor Kinetic's segmented chart of accounts — a natural account segment plus up to twenty analytical segments — into D365's main account plus financial dimensions within an eleven-segment account structure, including the triage method for deciding what becomes a dimension, what collapses, and what retires.

What you will be able to do

Introduction

Epicor Kinetic's chart of accounts is a segmented account string. The natural (main) segment identifies the account — revenue, expense, asset, liability, equity — and up to twenty further analytical segments classify the posting along operational lines: division, department, cost centre, project, product line, location, and whatever else…

The Epicor segmented COA model

Each Epicor Company owns its chart of accounts. The COA is defined as a segmented string with a configurable number of segments — one natural (main) segment and up to approximately twenty analytical segments. The exact maximum is documented behind EpicWeb (Epicor's gated customer portal);

The D365 financial dimension model

D365's equivalent of Epicor's analytical segments is the financial dimension. A financial dimension is a named, independently defined attribute — Department, CostCentre, Project, BusinessUnit, ItemGroup — that can be attached to any posted transaction. There is no limit on how many financial dimensions you define;

The four-category triage method

The segment-compression exercise is not a mechanical rename. Each Epicor analytical segment must be classified into one of four categories, and the choice for each determines what it becomes in D365:

Designing account structures and advanced rules

Once the triage is complete, the surviving dimensions (Categories A and C) must be assembled into one or more D365 account structures. The design principles:

Dimension defaulting: replacing GL Control–driven segment population

In Epicor, GL Controls populate segment values at posting time. A GL Control Type specifies the kind of lookup (by part class, by customer, by site), and a GL Control Code holds the account values that result. The segment values on a posted transaction are the output of this resolution chain.

Multiple account structures and the reconciliation obligation

D365 permits multiple account structures per legal entity. Each structure covers a range of main accounts and defines its own dimension set. At posting time, the system determines which account structure applies based on the main account, then validates the dimensions against that structure's rules.

Currency and the ledger object

Each Epicor Company operates in a base currency. The COA, the fiscal calendar, and the books are all scoped to the Company. In D365, each legal entity has exactly one ledger, and that ledger has exactly two configurable currencies:

Knowledge check

Summary

Segment compression is the defining financial architecture decision in an Epicor Kinetic migration. It is not a technical exercise — it is an analytical exercise with reporting-continuity consequences that require management sign-off.