Mapping the two-company model to legal entities and dimensions

How to resolve Infor LN's dual Logistic-Company / Financial-Company architecture into D365 legal entities, sites, operating units, and financial dimensions — and what each choice costs in intercompany complexity.

What you will be able to do

• Name LN's primary organisational concepts and their D365 equivalents
• Apply the three unbundling patterns to a given LN company topology
• Explain how the enterprise-unit-to-financial-company binding drives the financial posting chain
• Describe the intercompany trade implications of each unbundling pattern
• Identify the dimensions required to preserve Logistic Company identity in management reporting

Introduction

Organisational modelling is the decision that every other design decision depends on. Get it wrong and the consequences cascade through chart of accounts, dimension structure, intercompany configuration, and the IMS translation.

LN's primary organisational concepts

LN organises operational and financial reality around eight primary concepts. Each one demands a D365 answer.

The enterprise-unit-to-financial-company binding

Understanding the enterprise unit is essential to understanding how LN's posting chain works. The enterprise unit sits between the Logistic Company and the Financial Company. Every logistic transaction is tagged with an enterprise unit;

The three unbundling patterns

The unbundling decision is the highest-impact structural choice in an LN migration. Every posting profile, every intercompany rule, and the entire data load sequence depends on it.

Multi-company and intercompany implications

The unbundling pattern determines not just how many legal entities you create but which intercompany mechanisms apply to cross-entity transactions.

Knowledge check

Summary

LN's organisational model is more layered than D365's, and collapsing it correctly is the prerequisite for every other migration decision.