Financial Consolidations in Microsoft Dynamics 365 for Finance and Operations — Lesson 2: Legal Entities, Charts, Currencies and Elimination Rules

Learning Objectives

• Map charts of accounts, dimensions, fiscal periods, exchange rates, and translation methods
• Configure intercompany identification, elimination rules, accounts, and adjustment policies
• Validate legal entities, charts, currencies and elimination rules decisions with documented requirements, test evidence, risk controls, and measurable acceptance criteria

Detailed Topics

• Map charts of accounts: Map charts of accounts, dimensions, fiscal periods, exchange rates, and translation methods
• Configure intercompany identification: Configure intercompany identification, elimination rules, accounts, and adjustment policies
• Validate legal entities: Validate legal entities, charts, currencies and elimination rules decisions with documented requirements, test evidence, risk controls, and measurable acceptance criteria

Guided Demonstration

1. Review the requirement, users, data, dependencies, permissions, risks, and expected result.
2. Demonstrate the relevant configuration, creation, administration, analysis, automation, or security workflow step by step.
3. Capture settings, outputs, logs, screenshots, calculations, test results, and other useful evidence.
4. Compare the observed result with acceptance criteria and explain any corrective action.

Hands-On Activity

Configure and validate core consolidation mappings and rules.

• Document assumptions, prerequisites, and the planned sequence before starting.
• Complete the activity and preserve evidence of normal, boundary, and failure behavior.
• Record issues, corrective actions, reusable notes, and the next improvement priority.

Scenario Analysis

• Identify the business or technical decision that must be made.
• Compare valid implementation approaches and their trade-offs.
• Consider security, privacy, accessibility, performance, support, and operational impact.

Troubleshooting Focus

• Separate symptoms from causes and collect evidence before applying a fix.
• Check configuration, data, permissions, dependencies, capacity, connectivity, and recent changes.
• Validate rollback, recovery, ownership, user impact, and business continuity.

Validation Checklist

• The requirement, scope, inputs, and expected outcome are clear.
• The selected design or configuration is documented and follows approved standards.
• Normal, boundary, failure, security, accessibility, and operational conditions are reviewed.
• The result is supported by evidence and the next improvement is prioritized.

Lesson Outcome

Learners can explain and apply Legal Entities, Charts, Currencies and Elimination Rules in a realistic scenario and validate the result with documented evidence.