Study guide
1.2 Dynamics 365 Finance Architecture, Legal Entities & Global Address Book
Microsoft Certified: Dynamics 365 Finance Functional Consultant Associate MB-310
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: MB-310 Exam Overview & Financial Architecture
1.1 MB-310 Exam Structure, Skills Measured & Consultant Role 1.2 Dynamics 365 Finance Architecture, Legal Entities & Global Address Book 1.3 Hands-on Lab Strategy & Preparation Framework
2 Chapter 2: Chart of Accounts & Main Accounts
2.1 Designing Chart of Accounts & Main Account Types 2.2 Main Account Categories & Ledger Account Aliases 2.3 Balance Control Accounts & Year-End Opening Account Setup 2.4 Legal Entity Overrides for Main Accounts & Dimensions
3 Chapter 3: Financial Dimensions & Account Structures
3.1 Custom & Entity-Backed Financial Dimensions 3.2 Financial Tags: Limits, Storage & Ledger Settlement Use 3.3 Account Structures, Segment Criteria & Activation 3.4 Advanced Rules & Advanced Rule Structures 3.5 Derived Dimensions & Dimension Default Templates
4 Chapter 4: Ledgers, Calendars & Currencies
4.1 Fiscal Calendars, Period Statuses & Module Access Control 4.2 Posting Layers, Multi-GAAP Reporting & the Ledger Form 4.3 Currency Exchange Types, Rate Providers & Triangulation 4.4 Accounting & Reporting Currencies (Dual-Currency Architecture) 4.5 Foreign Currency Revaluation & Revaluation Posting Profiles
5 Chapter 5: General Ledger Journals & Allocations
5.1 Journal Names & Voucher Number Sequences 5.2 Journal Control & Posting Restriction Rules 5.3 Journal Entry, the One-Voucher Rule, Validation & Posting 5.4 Reversals, Storno Corrections & Excel Integration 5.5 Ledger Allocation Rules & the Four Allocation Methods 5.6 Allocation Processing & Periodic (Recurring) Journals
6 Chapter 6: Intercompany Accounting & Settlements
6.1 Intercompany Accounting Setup & Due-To / Due-From Postings 6.2 Intercompany Journal Processing & Multi-Company Vouchers 6.3 Ledger Settlements Configuration & Processing
7 Chapter 7: Cash and Bank Management
7.1 Bank Groups, Bank Accounts & Ledger Integration 7.2 Payment Formats, Bank FX Revaluation & Shared Payment Setup 7.3 Manual vs. Advanced Bank Reconciliation & Statement Formats 7.4 Matching Rule Sets, Reconciliation Execution & Reversals 7.5 Cash Flow Forecasting Setup & Automation 7.6 Customer and Vendor Netting
8 Chapter 8: Periodic Closing & Financial Consolidations
8.1 Financial Period Close Workspace, Closing Roles & Schedules 8.2 Year-End Close Configuration & General Ledger Balance Carryforward 8.3 Consolidations Online: Legal Entity Setup, COA Mapping & Currency Translation 8.4 Import Consolidations & Intercompany Elimination Rules
9 Chapter 9: Sales Tax & Withholding Tax
9.1 Sales Tax Engine Hierarchy, Authorities & Settlement Periods 9.2 Ledger Posting Groups, Sales Tax Codes & Calculation Methods 9.3 Sales Tax Groups, Item Sales Tax Groups & Tax Exemptions 9.4 Sales Tax Adjustments and Settle and Post Sales Tax 9.5 Withholding Tax & US 1099 Vendor Reporting
10 Chapter 10: Accounts Receivable Setup & Invoicing
10.1 Customer Master, Customer Groups & Shared Customers 10.2 Customer Posting Profiles & Account Code Precedence 10.3 Free Text Invoices, Recurring Invoice Templates & AR Charges 10.4 Sales Order Invoicing, Billing Classifications & Prepayments 10.5 Customer Payment Methods, Payment Processing & Customer Bank Accounts
11 Chapter 11: Credit Management & Collections
11.1 Credit Management Architecture & Customer Credit Groups 11.2 Risk Scoring, Credit Limits, Blocking Rules & Credit Holds 11.3 Aging Definitions, Collections Workspace & Customer Pools 11.4 Collection Letter Sequences & Interest Notes 11.5 Customer Write-Offs, Bad Debt & Write-Off Reversals
12 Chapter 12: Subscription Billing & Revenue Deferrals
12.1 Recurring Contract Billing, Billing Schedules & Milestones 12.2 Deferral Principles, Deferral Defaults & Schedule Calculation Methods 12.3 Recognition Processing, Expense Deferrals & Modifying Schedules 12.4 Multiple Element Revenue Allocation (MEA / ASC 606)
13 Chapter 13: Accounts Payable & Invoice Processing
13.1 Shared Vendors, Global Address Book & Vendor Groups 13.2 Vendor Posting Profiles, AP Parameters & Vendor Bank Accounts 13.3 Invoice Matching Setup (2-Way, 3-Way), Tolerances & Exceptions 13.4 Vendor Invoicing Methods, Journals & Invoice Automation
14 Chapter 14: Vendor Payments & Expense Management
14.1 Methods of Payment & the Vendor Payment Proposal Engine 14.2 Generating Payments, Centralized Payments & Check Lifecycle 14.3 Expense Management Configuration, Categories & Policies 14.4 Expense Reports Processing, Mobile Receipts & Intercompany Expenses
15 Chapter 15: Budgeting & Budget Control
15.1 Budget Models, Budget Codes & Allocation Terms 15.2 Budget Register Entries, Workflows & Budget vs. Actual 15.3 Budget Transfer Rules & Processing Budget Transfers 15.4 Budget Control Configuration, Cycles, Rules & Budget Groups 15.5 Budget Funds Available, Over-Budget Permissions & Document Budget Check 15.6 Budget Planning Framework, Organization Hierarchies & Planning Processes 15.7 Budget Plans, Scenarios, Allocations & Generating Register Entries
16 Chapter 16: Fixed Assets Configuration & Transactions
16.1 Fixed Asset Groups, Asset Records & Group/Book Mapping 16.2 Depreciation Profiles: Methods & Conventions 16.3 Fixed Asset Books, Derived Books & Posting Profiles 16.4 Fixed Asset Acquisition Pathways 16.5 Depreciation Proposals, Multi-Company Runs & Fixed Asset Budgets 16.6 Fixed Asset Disposals: Sale, Scrap & Disposal Accounting 16.7 Fixed Asset Splits, Transfers & Reclassification 16.8 Asset Leasing (IFRS 16 / ASC 842)
1.2 Dynamics 365 Finance Architecture, Legal Entities & Global Address Book
Key Takeaways Explain This Topic AI
Legal Entities (DataAreaId) enforce independent legal jurisdictions, ledgers, and tax registrations, whereas Operating Units structure organizational hierarchies for management reporting without data segregation.
The Global Address Book (GAB) implements a polymorphic Party model (Person or Organization) that unifies identity, address, and contact records across multiple legal entities.
Number Sequences provide unique identifiers across Shared, Legal Entity, Operating Unit, or Fiscal Period scopes, with Continuous numbering preventing statutory gaps at the expense of posting throughput.
Organization Hierarchies serve distinct operational purposes, including financial dimension validation, centralized AP/AR payments, and configurable managerial approval workflows.
System administration parameters—such as System Currency, Document Routing, and the Batch Framework—establish the bedrock for reliable multi-company financial operations.
Last updated: August 2026
1.2 Dynamics 365 Finance Architecture, Legal Entities & Global Address Book
Quick Summary: Enterprise financial architecture in Dynamics 365 Finance relies on three foundational pillars: the Legal Entity structure (which establishes legal boundaries and fiscal ledgers), the Global Address Book (which unifies party identities across legal borders), and Number Sequences (which enforce statutory document numbering). Mastering the architectural interaction between legal entities, operating units, party roles, and system parameters is essential for both the MB-310 exam and real-world solution design.
1. Enterprise Architecture: Legal Entities vs. Operating Units
When designing an enterprise organization in Dynamics 365 Finance, the most critical architectural decision is determining what should be modeled as a Legal Entity versus an Operating Unit . +-----------------------------------------------------------------------------------+
- | Enterprise Organizational Structure |
- +-----------------------------------------------------------------------------------+
- | Shared Platform Layer (Global Address Book, Chart of Accounts, Users, Security) |
- +-----------------------------------------------------------------------------------+
- | LEGAL ENTITY: USMF (USA) | LEGAL ENTITY: DEMF (Germany) |
- | - Ledger: USD / US GAAP | - Ledger: EUR / German HGB & VAT |
- | - DataAreaId = 'usmf' | - DataAreaId = 'demf' |
- | +---------------------------------------+ | +---------------------------------+ |
- | | Operating Units (Financial Dimensions)| | | Operating Units | |
- | | - Business Unit: BU01 (Retail) | | | - Business Unit: BU02 (Mfg) | |
- | | - Department: DEP10 (Finance) | | | - Cost Center: CC40 (HQ) | |
- | | - Cost Center: CC10 (Marketing) | | +---------------------------------+ |
- | +---------------------------------------+ | |
- +-----------------------------------------------------------------------------------+
- Definitions & Structural Roles
Legal Entity ( DataAreaId ): An organization that is registered with legal authorities and required to publish standalone financial balance sheets, profit and loss statements, and statutory tax filings. Every legal entity is assigned a 4-character identifier in the database ( DataAreaId ) that partitions transactional tables (e.g., CustTable , VendTable , LedgerJournalTable ).
Operating Unit: An internal organizational division created for operational control, management reporting, and cost tracking. Operating units do not partition database tables; instead, they are shared across the entire environment and linked to legal entities via Financial Dimensions and Organization Hierarchies .
Operating Unit Types in D365 Finance
Business Units: Semi-autonomous operational divisions (e.g., Automotive, Electronics, Consulting ).
Cost Centers: Units responsible for operational expenses (e.g., Marketing, IT Support, Human Resources ).
Departments: Functional areas with specific operational tasks (e.g., Accounts Payable, Quality Assurance ).
Value Streams: Lean manufacturing or operational flow sequences.
Custom Operating Units: Defined by consultants to model industry-specific segments (e.g., Brands, Regions, Product Lines ).
Architectural Comparison: Legal Entity vs. Operating Unit
Architectural Attribute Legal Entity ( Company / DataAreaId ) Operating Unit ( Financial Dimension )
Database Partitioning Transactions stamped with specific DataAreaId . Shared global records ( OMOperatingUnit ); stamped as dimension strings.
General Ledger Owns a dedicated Ledger setup (COA, Calendar, Currency). Operates within the Ledger of the parent Legal Entity.
Statutory Tax Registration Possesses independent Tax IDs, VAT numbers, and filings. Cannot file independent statutory tax returns.
Intercompany Accounting Transactions between legal entities require Intercompany Due-To / Due-From postings. Cross-unit transactions generate self-balancing dimension balancing lines within a single entity.
Master Data Sharing Master data (Customers/Vendors) is entity-specific (referencing GAB party). Master data is globally shared across all legal entities.
Cross-Company Invoicing Requires intercompany trade orders or intercompany journals. Standard journal or invoice lines tagged with different dimension values.
Tip
Consultant Design Rule: Never create a Legal Entity solely to achieve departmental or regional reporting. If two divisions share the same statutory tax registration and legal charter, model them as Operating Units (e.g., Business Units or Cost Centers) and enforce balance-sheet reporting using Balancing Financial Dimensions in the General Ledger.
2. Organization Hierarchies & Purposes
Dynamics 365 Finance allows you to assemble legal entities and operating units into tree-structured Organization Hierarchies . Each hierarchy is assigned one or more Purposes that dictate how the hierarchy is consumed by system engines:
Security: Governs user data access and record-level security based on organization nodes.
Organization Dimension Control: Dynamically filters which operating units are available for selection in financial dimension dropdowns based on the selected legal entity.
Centralized Payments (AP/AR): Authorizes a parent legal entity to process vendor invoices or customer payments on behalf of subsidiary legal entities.
Workflow Approval Routing (Expenditure Reviewers): Determines the managerial hierarchy for purchase requisition and vendor invoice approvals based on Department or Cost Center ownership.
Budgeting: Enforces budget planning and budget control roll-ups across organizational branches.
3. Global Address Book (GAB) Architecture
The Global Address Book (GAB) is a shared, polymorphic repository that stores party, address, and contact information across the entire D365 environment, eliminating duplicate records across multiple legal entities. +---------------------------------+
- | GAB PARTY RECORD |
- | Party ID: 000004521 |
- | Name: Contoso Logistics GmbH |
- | Type: Organization |
- +---------------------------------+
- |
- +---------------------------+---------------------------+
- | | |
- v v v
- +------------------+ +------------------+ +------------------+
- | CUSTOMER ROLE | | VENDOR ROLE | | CONTACT ROLE |
- | Entity: USMF | | Entity: DEMF | | Entity: USRT |
- | Account: C-1001 | | Account: V-9002| | Contact ID: 881|
- +------------------+ +------------------+ +------------------+
- Party Record Model: Person vs. Organization
Every entity in the GAB is classified under one of two core Party types:
Person: Represents a unique individual (e.g., Worker, Applicant, Contact, Prospect, Customer ).
Organization: Represents a structured entity (e.g., Legal Entity, Vendor, Customer, Prospect, Competitor ).
Multi-Role Association
A single GAB party record can maintain multiple roles across multiple legal entities simultaneously without duplicating contact or address data:
Party 000004521 ( Contoso Logistics ) can exist as Customer US-004 in company USMF and as Vendor DE-009 in company DEMF .
Updating the primary address on the Party record automatically propagates the new address to both the customer and vendor master forms in their respective legal entities.
Address & Contact Mechanism
Address Purposes: Addresses are assigned one or more specific purposes (e.g., Delivery, Invoice, Remit-To, Payment, Business, Home, Consignment ). Posting engines automatically select the correct address based on transaction context (e.g., Free Text Invoice selects Invoice purpose; Sales Order packing slip selects Delivery purpose).
Effective Dating: Address records support validity date intervals ( Effective Date to Expiration Date ), allowing planned future address updates without breaking historical audit trails.
Private Flag: Restricts address visibility to authorized human resource workers or designated personnel.
Party Merging & De-duplication
When duplicate party records are inadvertently created, consultants can utilize the Merge Parties tool:
One party is designated as the Master Party Record .
All historical transactions, open customer/vendor accounts, and contact records from the subordinate party are re-linked to the master party.
The subordinate party record is permanently retired or deleted.
4. Number Sequence Architecture
Number sequences generate unique, readable identifiers for master data records (Customers, Vendors, Fixed Assets) and transactional documents (General Ledger Vouchers, Purchase Orders, Sales Invoices). +-----------------------------------------------------------------------------------+
- | Number Sequence Parameter Model |
- +-----------------------------------------------------------------------------------+
- | Format: INV-#####-[Company] --> Generates: INV-00001-USMF |
- | Segments: Constant (INV-) + Alphanumeric (#####) + Company Segment (USMF) |
- +-----------------------------------------------------------------------------------+
- | Allocation Type: |
- | - Continuous: Zero gaps allowed. Deleted numbers saved to Status List. |
- | - Non-Continuous: High performance. Numbers pre-allocated in cache. May have gaps|
- +-----------------------------------------------------------------------------------+
- | Scope Hierarchy: Shared -> Legal Entity -> Operating Unit -> Fiscal Period |
- +-----------------------------------------------------------------------------------+
- Number Sequence Scopes
The scope determines how broadly a number sequence applies across the system:
Shared: The sequence is globally shared across all legal entities (e.g., Party ID, Worker Personnel Number ).
Company / Legal Entity: The sequence generates unique numbers partitioned by DataAreaId (e.g., Customer Account, Vendor Account, General Journal Voucher ).
Operating Unit: Partitioned by specific operating units (e.g., Retail Store transaction numbers ).
Legal Entity + Fiscal Calendar Period: Automatically resets numbering at the start of each fiscal year or period (e.g., Tax Invoices in European/Latin American localizations ).
Continuous vs. Non-Continuous Allocation
Parameter Continuous Number Sequence Non-Continuous Number Sequence
Gaps in Numbering Strictly prohibited. Every generated number must be accounted for. Gaps permitted. Aborted or deleted records leave unassigned gaps.
Mechanism & Status List If a user aborts a transaction, the number is stored in a Status List and re-used for the next transaction. Numbers are pre-allocated in memory cache (e.g., blocks of 20); aborted numbers are discarded.
Performance Impact Higher latency / DB lock contention. Transactional locking occurs on the sequence table. High performance & throughput. Ideal for high-volume batch and retail operations.
Regulatory Requirement Mandatory for legal tax invoices, sales invoices, and official VAT vouchers in many countries. Standard for purchase orders, sales orders, quotes, and internal draft journals.
Caution
Setting high-volume transactional journals (like General Ledger recurring journals or retail point-of-sale journals) to Continuous can cause severe database locking and concurrency deadlocks. Only enable Continuous when legally required by local tax authorities.
5. System Administration Parameters Affecting Financials
Key system-wide parameters configured in System Administration directly govern financial reliability:
System Currency & System Exchange Rate Type: Configured under System parameters . Used for cross-company financial reporting and enterprise consolidations when individual legal entities use different accounting currencies.
Document Management Parameters: Configures Azure Blob Storage or SharePoint integration for attaching supporting vendor invoice PDFs, receipts, and contracts to journal vouchers.
Batch Job Processing Framework: Financial engines (e.g., Subledger journal transfer, Foreign currency revaluation, Depreciation proposals, Recurring billing schedules ) run as asynchronous batch tasks. Proper configuration of Batch Groups and execution windows prevents batch server memory contention during fiscal period-end closes.