Work the tenant, branch, site and warehouse topology into an explicit D365 environment and legal-entity design, and understand why interbranch accounting either disappears into dimensions or becomes a full intercompany framework.
Every module in this path depends on one decision, and this is the module where that decision gets made. What becomes a D365 environment, what becomes a legal entity, what becomes a site or warehouse, and what becomes a financial dimension?
An Acumatica tenant is a data-isolation and administrative boundary within an instance. Tenants exist for reasons that are usually historical and rarely uniform across one estate:
The branch is the harder half. The concept note lists five things a branch can mean, and the difficulty is that estates use several of them at once without labelling which is which.
Run it as a workshop with finance, operations and IT security in the room together, because the five meanings above map to those three constituencies and no single one of them can answer for the others.
The environment is the D365 deployment boundary. Multiple legal entities live inside one environment and share a great deal by design: the chart of accounts, financial dimensions where configured as shared, products, address book parties, integration governance and — importantly — release cadence.
Acumatica supports interbranch accounting through due-to and due-from clearing accounts that keep branch-level balances square. The posting-rules source flags this as relevant only where interbranch accounting is actually used, and rates it medium confidence for that reason — it is one of the tenant-specific behaviours that must be…
The inventory topology is a separate design from the accounting topology, and this is where estates most often lose control.
The classification only protects the programme if it is written down in a form other workstreams can be held to. A usable topology record contains, per source object:
Tenant and branch boundaries are not interchangeable with D365 environment and legal-entity design, and treating them as if they were is the characteristic Acumatica migration failure. A tenant is an isolation boundary that may hold one statutory unit, several, or none.