Legal entity setup in Dynamics 365 Finance

A legal entity in Dynamics 365 Finance is the unit of statutory accounting — one set of statutory books, one tax ID, one consolidated set of financial statements. Configuring a new legal entity is a substantial implementation task; understanding the layers of setup is essential to getting it right.

Identity and incorporation.

• Name — the formal legal name as registered.
• Legal entity ID — a short code used throughout F&O.
• Address — the registered office.
• Country — drives statutory regulations and the country localisation.
• Tax registration numbers — VAT, EIN, country-specific tax IDs.
• Currency — the entity's primary statutory currency.
• Reporting currency — optional secondary currency for group-level reporting (see the parallel currencies guide).

Country localisation. Each legal entity belongs to a country whose localisation drives much of the configuration:

• Tax engine setup — VAT codes, sales tax codes, withholding tax codes per country regulations.
• Statutory reports — VAT returns, intrastat, SAF-T, country-specific filings.
• Electronic reporting (Globalization Studio) configurations — for e-invoicing, payment files, tax submissions per country format.
• Document layouts — invoice templates conforming to country statutory format.
• Number sequences — some countries require continuous, gap-free sequences for invoices.

Microsoft ships localisations for ~20 countries; partner localisations cover most others.

Chart of accounts. Each entity references a chart of accounts:

• Shared across entities — common in multi-entity groups where consolidation matters. The shared CoA simplifies eliminations and reporting.
• Per-entity CoA — when entities have substantially different account structures (different industries, different countries with different statutory account standards).

In F&O, the CoA is independent of the entity; one CoA can serve many entities. Choose the model deliberately at implementation.

Account structures and posting profiles. Beyond the CoA, the account structure defines required dimensions per posting (see the financial dimensions guide). And posting profiles map sub-ledger transactions to GL accounts:

• Customer posting profile — how AR settlements hit the GL.
• Vendor posting profile — how AP settlements hit the GL.
• Inventory posting profile — how inventory movements hit the GL.
• Fixed asset posting profile — how depreciation, acquisition, and disposal hit the GL.
• Project posting profile — how project costs and revenue hit the GL.

Each profile is configured per legal entity per scenario; designing them takes substantial implementation time.

Dimension structure. Each entity references a dimension structure — Department, Cost Centre, Project, Region, etc. Multi-entity tenants commonly share dimensions for consistent reporting but can vary per entity where structures differ.

Bank accounts. Each entity has its own bank accounts:

• Operating accounts.
• Payroll accounts.
• Escrow / trust accounts.
• Tax-remittance accounts.
• Intercompany accounts.

Bank account configuration includes the bank's name, account number, IBAN, payment file formats, statement formats.

Vendor and customer master data. Each entity has its own:

• Customer master — though many customers can be shared across entities through shared services or master data management patterns.
• Vendor master — same; shared common vendors with per-entity payment terms and bank details.

Employees and workforce. Workers can be associated with one or more entities — common when staff perform work across entities. Time sheets and expenses can post to projects in different entities.

Intercompany. For multi-entity operations:

• Intercompany counterparties — defined per legal entity pair, specifying GL accounts for IC postings.
• Intercompany sales / purchases — automatically generate counter-documents in the partner entity.
• Centralised payments — one entity can pay vendor invoices for another entity, with IC accounting reconciling.

Consolidation. Multi-entity groups consolidate into a consolidation company — a special entity that aggregates subsidiary results into group financial statements:

• Each subsidiary uploads its trial balance to the consolidation entity.
• Currency translation applies (different entities may have different statutory currencies).
• Eliminations remove intercompany transactions.
• Adjustments apply for group-specific accounting policies.

Implementation sequence.

1. Establish the country localisation foundations.
2. Configure CoA, dimensions, account structures.
3. Configure posting profiles for all relevant sub-ledgers.
4. Set up bank accounts, vendors, customers (typically through migration).
5. Configure tax (VAT, sales tax, withholding) per country requirements.
6. Configure financial reporting and statements per local statutory format.
7. Configure intercompany if multi-entity.
8. Validate through cycle 1 of mock posting before go-live.

Common pitfalls.

• Underestimating localisation setup time — each new country can be weeks of work.
• Inconsistent CoA across entities — consolidation breaks; manual reconciliation perpetually.
• Wrong posting profiles — every transaction posts to the wrong account; year-end reveals the damage.
• Missing tax setup — invoices post with wrong VAT; statutory filings inaccurate; penalties accumulate.

Operational reality. Setting up a new legal entity is a 2–6 week implementation effort for a country with a strong localisation; 2–4 months for countries with partial coverage; longer for greenfield localisations. Plan accordingly when expanding internationally.