Legal entities and master data in Dynamics 365 F&O

Station two built an execution plan. This station is the foundation the remaining seven stand on.

What makes it heavy is that most of its decisions are final. A supplier name changes a thousand times. A financial dimension that was never created yields no report two years later.

The four layers

Layer	What it is	What hangs off it
Legal entity	The registered company, with its own books	Journals, financial statements, the tax number
Ledger	Calendar, currency and account structure	Posting and the close
Operating units	Department, cost centre, business unit	Analysis and accountability
Intercompany relationships	Trading relationships between entities	Intercompany sales and consolidation

The distinction to master: a legal entity is what you issue statutory accounts for; an operating unit is what you issue an internal performance report for. Confuse them and you create a legal entity per branch, then find yourself closing ten sets of books a month instead of one.

Main accounts and financial dimensions

This is the biggest structural difference between this product and what somebody arriving from a simple accounting package is used to.

In the simple package, the account number carries everything. 510101 becomes salaries expense, Riyadh branch, sales department, and the chart grows to three thousand accounts.

Here the main account carries the nature of the expense alone, and everything else is an independent financial dimension attached to the journal.

Element	Example	How many values
Main account	Salaries expense	One
Dimension: branch	Riyadh, Jeddah, Dubai	Three
Dimension: department	Sales, production, admin	Three
Dimension: project	As needed	Variable

One account instead of nine. And a report can be cut at any intersection of them without creating a new account.

The account structure decides which dimension is mandatory against which account. Leave everything optional and half your journals carry no dimension, so no report can be produced — which is the commonest design failure in this product, and it surfaces only after six months.

Advanced rules allow a sharper condition: the project dimension mandatory on expense accounts only, for instance. Write them into the design rather than after the first incomplete report.

The decisions with no way back

Decision	Why it is final
The number and names of dimensions	A dimension never created cannot be backfilled into past journals
The fiscal calendar and its periods	Extra periods are defined at creation
The entity’s currency	Fixed with the first journal
Number sequences	Changeable, but old documents keep their numbering — so you get two series

Number sequences are underestimated and paid for in front of an auditor: sales invoice numbering in Saudi Arabia must run in sequence without gaps, and anybody who designed it thoughtlessly explains gaps at every review.

The four master data objects

Object	What to master
Vendors	The vendor group decides the posting profile — which payables account it lands in
Customers	Likewise, and the customer group carries payment terms and credit
Items	The item model group decides the costing method, and the posting group decides the inventory accounts
Units of measure	Class, units and conversion rules, set before the first purchase

The word “group” in every row is the whole key. The system does not ask the user for an account; it derives one from the group. Configure the groups correctly and you get correct journals with no intervention. Neglect them and you get journals corrected by hand every month.

The item model group in particular carries the costing decision, which is station six, and changing it once transactions exist is a project rather than a setting.

What this structural depth costs — what is actually being paid for — is in the Dynamics 365 Finance & Operations guide.

Number sequences — a small setting with a statutory effect

This setting looks like administrative detail and is the most asked about at audit.

Three decisions sit in it.

• Scope: is the sequence per company, per branch, or per group? The answer comes from the tax regime in your country rather than from preference.
• Continuity: are gaps permitted? In Saudi Arabia the answer is no for tax invoices — as in the e-invoicing station.
• Continuation from the legacy system: do you start at one, or from where the old system stopped?

The third is usually taken without thought and regretted. Starting at one is clean and clear, but it produces a duplicate invoice number across the two systems within the same tax year — which an accountant then explains at every audit for years.

The rule: statutory document sequences continue from where they stopped, and internal document sequences start afresh. Which document is which goes into the design document, rather than being left to whoever creates the sequence on configuration day.

This station’s exercise

On paper, before any screen.

1. A group with a Riyadh company in riyals and a Dubai company in dirhams. How many legal entities, and how many ledgers?
2. Write the main accounts for a services company’s expenses — forty at most.
3. Write the financial dimensions, justifying each one with a report asked for today. Delete any with no report.
4. Write the account structure: which dimension is mandatory against which account category, and why.
5. Write one advanced rule: a condition making a dimension mandatory in one specific case.

What you actually do in this station

• Finish the account structure and dimensions units of “configure financial management” on Microsoft Learn.
• Do the exercise in writing — five pages.
• Execute it in the trial environment if it is open, and otherwise document it in writing.
• Show your design to an accountant working in a group and ask: which report does your management ask for that you cannot produce? The answer reveals the missing dimension.
• Revisit ERP modules to connect the layers to what sits above them.

The three commonest mistakes

One: porting an old chart of accounts as it stands. Three thousand accounts land in a system designed to run on forty accounts and four dimensions, and the whole advantage is lost on day one.

Two: leaving dimensions optional. Half the journals carry none, reports cannot be produced, and it is found six months later.

Three: neglecting posting groups. What could be derived automatically gets corrected by hand every month.

The acceptance test for this station

1. Distinguish a legal entity from an operating unit and when each is created.
2. Explain how main accounts and dimensions replace a bloated chart, with a numeric example.
3. Show your design and justify each dimension with a report.
4. Explain your account structure and your advanced rule.
5. Explain the item model group’s role and why changing it later is a project rather than a setting.

What comes next

The foundation is built. The next four stations run transactions through it, starting with the procurement cycle — requisition to supplier payment, and the matching policy with its tolerances.