Study guide
2.1 Designing Chart of Accounts & Main Account Types
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)
2.1 Designing Chart of Accounts & Main Account Types
Key Takeaways Explain This Topic AI
Dynamics 365 Finance utilizes a shared Chart of Accounts (COA) architecture where a single COA definition can be assigned to multiple legal entities in the Ledger form, drastically streamlining multi-entity maintenance.
Main Account Types determine core financial behavior and Year-End Close processing: Balance Sheet types (Asset, Liability, Equity) roll forward closing balances, while Profit & Loss types (Revenue, Expense) close into retained earnings.
The Total account type serves strictly as a reporting aggregator using interval or arithmetic expressions and rejects transactional postings, whereas Reporting accounts capture statistical and non-financial data.
The 'Do not allow manual entry' toggle is an essential internal control that blocks direct journal selection, forcing postings through subledger source documents (AP, AR, Fixed Assets, Inventory) to safeguard reconciliation integrity.
A structured, fixed-length numbering convention with logical digit prefixing (e.g., 100000–199999 for Assets) optimizes segment filtering, financial reporting hierarchies, and account structure rule evaluation.
Last updated: August 2026
2.1 Designing Chart of Accounts & Main Account Types
Quick Summary: The Chart of Accounts (COA) in Microsoft Dynamics 365 Finance is a shared structural master list of general ledger accounts used to classify, record, and report financial transactions. A single global COA can be shared across multiple legal entities or assigned individually per entity. Every main account must be configured with a specific Main Account Type , which dictates its normal debit/credit balance, its financial statement behavior, and its processing logic during the periodic Year-End Close .
1. Architectural Overview of the Chart of Accounts
In Microsoft Dynamics 365 Finance, the Chart of Accounts serves as the backbone of the General Ledger. Unlike legacy ERP systems that require duplicate COAs for every legal entity, Dynamics 365 Finance implements a global shared architecture .
Global Shared vs. Multi-COA Strategy
When designing an enterprise general ledger, functional consultants must determine the COA deployment model:
Shared Global Chart of Accounts (Recommended): A single master COA is created once and linked to multiple legal entities in their respective Ledger setup ( General ledger > Ledger setup > Ledger ). Legal entities share the identical main account list, while entity-specific behaviors (such as posting restrictions, default sales tax groups, and active dates) are managed through Legal Entity Overrides .
Multiple Independent Charts of Accounts: Separate COA records are created for entities with fundamentally incompatible statutory reporting requirements, distinct languages, or localized mandatory government account structures (such as France's Plan Comptable Général or Spain's Plan General de Contabilidad ).
Consolidation Chart of Accounts: When operating entities utilize disparate local COAs, a corporate consolidation COA is defined. Subsidiary main accounts map to corporate consolidation accounts using the Consolidation account field on the main account record, enabling seamless multi-entity consolidation without forcing operational restructuring. +-------------------------------------------------------------------------+
- | Global Shared Chart of Accounts |
- | (Shared_COA) |
- +-------------------------------------------------------------------------+
- | | |
- v v v
- +--------------------+ +--------------------+ +--------------------+
- | Legal Entity: USMF | | Legal Entity: DEMF | | Legal Entity: GBSI |
- | (Currency: USD) | | (Currency: EUR) | | (Currency: GBP) |
- | - Override: TaxGrp | | - Override: Suspnd | | - Override: ValGrp |
- +--------------------+ +--------------------+ +--------------------+
- System Navigation
To configure and manage the Chart of Accounts and Main Accounts:
- Chart of Accounts Definition: General ledger > Chart of accounts > Accounts > Chart of accounts
- Main Account Master Setup: General ledger > Chart of accounts > Accounts > Main accounts
- Ledger Assignment: General ledger > Ledger setup > Ledger
- 2. Main Account Types & System Behaviors
Every main account created in Dynamics 365 Finance requires a Main Account Type . This classification is not merely descriptive; it controls critical automated runtime processes, balance roll-forward mechanisms during Year-End Close, and standard financial reporting classification.
Detailed Account Type Matrix
Main Account Type Financial Statement Classification Normal Balance Year-End Close Behavior Direct Transaction Posting
- Asset Balance Sheet Debit Balance rolls forward to next fiscal year Yes
- Liability Balance Sheet Credit Balance rolls forward to next fiscal year Yes
- Equity Balance Sheet Credit Balance rolls forward to next fiscal year Yes
- Revenue Profit & Loss Credit Balance closes to Retained Earnings (zeroed out) Yes
- Expense Profit & Loss Debit Balance closes to Retained Earnings (zeroed out) Yes
- Total Header / Aggregator N/A Ignored during year-end close No (Posting Blocked)
- Balance sheet Balance Sheet (Generic) Debit / Credit Balance rolls forward to next fiscal year Yes
Reporting Statistical / Non-Financial Debit / Credit Ignored during year-end close Yes (Non-monetary or tracking)
Deep-Dive: Year-End Close Processing Logic
The fundamental distinction between Balance Sheet types ( Asset , Liability , Equity , Balance sheet ) and Profit & Loss types ( Revenue , Expense ) governs the automated Year-End Close process ( General ledger > Period close > Year end close ):
Balance Sheet Accounts: The closing ending balance of each balance sheet main account at the final period of Year N N N becomes the opening beginning balance of Period 0 (Opening Period) in Year N + 1 N+1 N + 1 . Financial dimension balances are preserved or summarized based on dimension transfer configurations.
Profit & Loss Accounts: All transactions posted to Revenue and Expense accounts across the fiscal year are aggregated. The net sum (Net Income or Net Loss) is posted as an opening entry into the designated Retained Earnings main account in Period 0 of Year N + 1 N+1 N + 1 . The opening balance for all P&L accounts in the new fiscal year is reset to 0.00 .
Total Accounts: Total accounts are structural calculation accounts. They display mathematical totals based on defined account intervals (e.g., 100000..199999 ) or expressions. Users cannot post general journals or subledger vouchers directly to a Total account.
Reporting Accounts: Used for non-financial or statistical tracking (such as employee headcount, square footage of retail space, or greenhouse gas emissions). They can hold transaction balances for reporting and allocation basis calculations without contaminating statutory balance sheet or P&L figures.
3. Account Numbering Conventions and Masking
A robust main account numbering structure is vital for long-term scalability, segment filtering in account structures, and automated financial report generation.
Numbering Best Practices
Fixed-Length Numeric Strings: Utilize a consistent character length across all accounts (e.g., 6 digits: 110110 ). Avoid variable lengths (mixing 4-digit and 6-digit accounts), which can cause alphanumeric sorting anomalies where 10000 sorts before 100 .
Logical Prefixing: Dedicate the leading digit to the primary account type to allow intuitive wildcard filtering (e.g., 1* for Assets, 5* for Operating Expenses) in account structures and financial reports.
Natural Expansion Gaps: Leave numerical gaps between accounts (e.g., numbering cash accounts 110100 , 110200 , 110300 rather than 110101 , 110102 ) to accommodate future acquisitions, specialized sub-accounts, or regulatory additions without disrupting logical groupings.
Standard 6-Digit Enterprise Numbering Schema
Number Range Account Classification Typical Sub-ranges Example Main Accounts
100000–199999 Assets 110000–119999: Cash & Equivalents; 120000–129999: Accounts Receivable; 130000–139999: Inventory; 150000–179999: Fixed Assets 110110 Operating Bank Account; 120100 AR Trade Payers; 130100 Raw Materials Inventory
200000–299999 Liabilities 210000–219999: Accounts Payable; 220000–229999: Accrued Expenses; 250000–269999: Long-Term Debt 210100 AP Trade Vendors; 220100 Sales Tax Payable; 250100 Senior Notes Payable
300000–399999 Equity 310000–319999: Common Stock; 320000–329999: Additional Paid-in Capital; 330000–339999: Retained Earnings 310100 Common Shares Issued; 330100 Retained Earnings Current
400000–499999 Revenue 410000–419999: Product Sales; 420000–429999: Service Revenue; 480000–489999: Discounts & Returns 410100 Commercial Product Sales; 420100 Consulting Services Revenue
500000–599999 Cost of Goods Sold 510000–519999: Direct Materials; 520000–529999: Direct Labor; 530000–539999: Overhead Absorbed 510100 COGS Finished Goods; 530100 Manufacturing Variance
600000–699999 Operating Expenses 610000–619999: Payroll & Benefits; 620000–629999: Rent & Utilities; 630000–639999: Travel & Entertainment 610100 Base Salaries & Wages; 620100 Office Facility Lease
700000–799999 Other Income / Expense 710000–719999: Interest Income; 720000–729999: Interest Expense; 750000–759999: FX Gain/Loss 720100 Commercial Debt Interest; 750100 Realized FX Gain/Loss
4. Lifecycle Controls: Active Dates, Suspended State & Manual Entry Restrictions
Maintaining data integrity across the General Ledger requires strict controls over when, how, and by whom main accounts can be utilized in transactions.
Temporal Validity: Active From and Active To
Located on the General FastTab of the Main accounts form, the Active from and Active to date fields restrict transaction posting based on the transaction date:
If a user attempts to post a journal voucher with a transaction date prior to the Active from date or past the Active to date, the posting engine throws an error and aborts posting.
These dates are evaluated globally for the shared COA unless overridden at the legal entity level.
Leaving the fields blank indicates perpetual validity.
Suspended vs. Do Not Allow Manual Entry (Critical Distinction)
A frequent source of exam confusion is the operational difference between the Suspended toggle and the Do not allow manual entry toggle: +------------------------------------------+
- | Incoming Transaction Attempt |
- +------------------------------------------+
- |
- +----------------------+----------------------+
- | |
- v v
- [ Source: Manual Journal ] [ Source: Subledger Posting ]
- (General Journal, Invoice Jnl) (Sales Inv, PO Invoice, FA)
- | |
- | |
- +--------------+--------------+ +--------------+--------------+
- | | | |
- v v v v
- [ Suspended = Yes ] [ Do Not Allow Man = Yes] [ Suspended = Yes ] [ Do Not Allow Man = Yes]
- | | | |
- X POSTING BLOCKED X POSTING BLOCKED | X POSTING BLOCKED | POSTING ALLOWED
- (Entire Account Disabled) (Manual Only Blocked) (Entire Account Disabled) (Subledger Control Intact)
- 1. Suspended Toggle ( Blocked )
When set to Yes , the account is completely frozen across the entire system.
No transactions of any kind can be posted to this account—neither manual general journals nor automated subledger distributions (AP invoices, AR billing, Inventory movements, Fixed Asset depreciation).
Primarily used when retiring obsolete accounts or preventing postings during audit investigations.
2. Do Not Allow Manual Entry Toggle
When set to Yes , users are blocked from selecting this main account in manual journal lines (e.g., General journals, Expense journals, Daily journals).
Crucially, automated subledger postings remain fully active. When a subledger transaction generates accounting distributions (such as posting a customer invoice via Accounts Receivable or an inventory receipt via Procurement), the posting profile successfully posts to the account.
Implementation Mandate: This toggle MUST be enabled for all subledger control accounts (e.g., Accounts Receivable Trade Control 120100 , Accounts Payable Trade Control 210100 , Inventory Control 130100 , Fixed Asset Control 150100 ). If left disabled, users could post manual general journals directly to the GL control account without updating the underlying subledger sub-tables, causing permanent reconciliation breaks between General Ledger trial balance and AP/AR aging subledgers.
5. Exam Traps & Real-World Best Practices
Warning
Exam Trap: Changing Main Account Type After Posting In Dynamics 365 Finance, changing the Main account type (e.g., from Expense to Balance sheet ) on an account that already contains posted transactional history is heavily restricted or can cause severe financial statement corruption during Year-End Close. If an account was misconfigured as Expense and transactions were posted, running Year-End Close will zero out its balance into retained earnings instead of rolling it forward. Always verify Main Account Type during initial design and test in sandbox environments prior to go-live!
Important
Consultant Pro-Tip: Global COA Edits vs. Legal Entity Overrides Edits made to the root Main Account record in General ledger > Chart of accounts > Accounts > Main accounts immediately impact every single legal entity sharing that Chart of Accounts. If a requirement dictates that Account 610500 (Consulting Expense) must be suspended only in the German entity ( DEMF ) while remaining active in the US entity ( USMF ), never flip the global Suspended flag on the Main Account header. Instead, navigate to the Legal entity overrides FastTab and create an entity-specific override for DEMF .