Study guide
3.3 Account Structures, Segment Criteria & Activation
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)
3.3 Account Structures, Segment Criteria & Activation
Key Takeaways Explain This Topic AI
An account structure can contain a maximum of 11 segments: one main account plus up to 10 financial dimensions (Microsoft Learn, Account structures overview).
Every account structure requires a main account segment, and a given main account value may exist in only one active structure on the ledger — otherwise activation reports overlapping criteria.
Each grid line holds a maximum of seven criteria per segment; use Duplicate to add more.
Criteria are compared as strings, not numbers, so 1000000 falls inside the range 100000..399999 unless values are zero-padded.
Separate multiple criteria values with semicolons — commas are valid characters inside a dimension value and silently collapse the entry into one truncated 30-character value.
Last updated: August 2026
3.3 Account Structures, Segment Criteria & Activation
In Dynamics 365 Finance, Account Structures provide the rules engine that determines which financial dimensions are required, optional, or prohibited when posting to specific Main accounts. Account structures ensure data integrity by preventing users from entering invalid dimension combinations (e.g., posting a Balance Sheet Cash transaction with a Manufacturing Cost Center) before transactions reach the General Ledger.
1. Account Structure Architecture & Constraints
Account structures are configured under General ledger > Chart of accounts > Structures > Configure account structures . +-----------------------------------------------------------------------------+
- | ACCOUNT STRUCTURE CONSTRAINTS |
- +-----------------------------------------------------------------------------+
- | 1. Segment 1 is ALWAYS MainAccount (Cannot be reordered or omitted) |
- | 2. Maximum 11 Segments total (MainAccount + up to 10 Financial Dimensions) |
- | 3. Left-to-Right Evaluation: Segment N restricts lookup values in N+1 |
- | 4. Non-Overlapping Rule: Main account ranges across multiple active |
- | structures attached to the same Ledger must NEVER overlap! |
- +-----------------------------------------------------------------------------+
- The Segment Capacity Limit
An account structure can contain a maximum of 11 segments (the MainAccount segment plus up to 10 financial dimension segments). If an organization requires more than 10 dimensions for a specific transaction scenario, Advanced Rule Structures must be used.
Multi-Structure Ledger Strategy
Rather than building a single monolithic account structure containing all main accounts and dimensions, best practice dictates splitting account structures by account classification (e.g., Balance Sheet vs. Operating Expenses vs. Revenue):
Balance Sheet Structure : MainAccount (100000..399999) -> BusinessUnit (Balance sheet accounts typically require minimal dimensional breakdown).
Revenue Structure : MainAccount (400000..499999) -> BusinessUnit -> Department -> SalesChannel .
Expense Structure : MainAccount (500000..899999) -> BusinessUnit -> Department -> CostCenter .
Critical Ledger Rule : When multiple account structures are added to a legal entity's Ledger ( General ledger > Ledger setup > Ledger ), the Main account criteria across all assigned structures must be mutually exclusive. If account 500100 appears in both the Expense Structure and an Intercompany Structure , the Ledger cannot be saved or will generate a validation error upon posting.
2. Segment Criteria, Operators & Wildcard Syntax
Segment criteria dictate which dimension values are permissible based on the preceding segments in the structure.
Operator / Syntax Syntax Example Meaning & Functional Behavior
Exact Value 110100 or ADMIN Only the specific value is valid.
Discrete List 110100, 110200, 110300 Any value in the comma-separated list is valid.
Inclusive Range 100000..199999 All values between and including the boundary values are valid.
Wildcard Match 6* or *CORP Matches any character string beginning with 6 or ending with CORP .
Blank Allowed "" (or select Blank allowed checkbox) Dimension can be left unpopulated (null) on transaction lines.
Exclusion / Negation !100 or !500000..599999 All values EXCEPT the specified value or range are permitted.
Wildcard + Specific * (All values) Any existing active dimension value is allowed.
Left-to-Right Hierarchical Evaluation
Dynamics 365 Finance evaluates account structure grids from left to right. When a user selects a value in a parent segment (e.g., BusinessUnit = '001' ), the lookup for the subsequent segment ( Department ) is dynamically filtered to show only those departments permitted by the row containing BusinessUnit = '001' . Row 1: MainAccount: 600000..699999 | BusinessUnit: 001 | Department: DEP-10..DEP-19 | CostCenter: *
Row 2: MainAccount: 600000..699999 | BusinessUnit: 002 | Department: DEP-20..DEP-29 | CostCenter: CC-01
In this configuration, selecting BusinessUnit = 001 restricts Department lookups to DEP-10 through DEP-19 . Entering DEP-20 will trigger an immediate account structure validation error during journal entry.
3. The Activation Lifecycle & Batch Processing
When creating or modifying an account structure, changes are stored in a Draft schema. The active version continues to govern live postings until explicit activation occurs. +-----------------------------------------------------------------------------+
- | ACCOUNT STRUCTURE ACTIVATION LIFECYCLE |
- +-----------------------------------------------------------------------------+
- | [1. Draft State] --> [2. Validate] --> [3. Activate Batch Job] |
- | - Make edits - Check overlaps - Compiles validation trees |
- | - Add/remove segments - Check syntax - Updates unposted combinations |
- | |
- | Status: Draft Status: Validating Status: Active |
- +-----------------------------------------------------------------------------+
- Activation Mechanics
Clicking Activate triggers a validation routine that checks for logical contradictions and range collisions.
The system submits a batch job ( DimensionHierarchyActivationValidation ).
The activation process updates the compiled dimension hierarchy tree in the database and evaluates existing unposted journal lines against the new criteria.
Production Consideration : Activating account structures in a high-transaction environment can cause table locks on DimensionAttributeValueCombination . Activations should always be scheduled during maintenance windows or low-activity periods.
4. Criteria Syntax Traps That Decide Exam Answers
Microsoft documents four criteria behaviours that are counter-intuitive and heavily tested.
1. Comparison Is String-Based, Not Numeric
The system compares all criteria as strings . Character-by-character comparison means the seven-digit value 1000000 falls inside the six-digit range 100000..399999 , even though 1,000,000 is numerically far larger than 399,999. If account numbers of differing length exist, zero-pad the range ( 0100000..0399999 ) so the comparison behaves as intended.
2. Semicolons Separate Values — Commas Do Not
Commas are valid characters inside a dimension value , so a comma-separated list is read as one single value and truncated to the 30-character dimension value maximum. Entering: 40000,49999,50000,52999,55000,59999
is interpreted as one "through" value — 40000 through 49999.50000..52999.55000..5999 — silently clipped at 30 characters. The correct delimiter is the semicolon . Always confirm the interpretation in the Allowed value details pane below the grid, which renders each criterion as a readable sentence.
3. Wildcards Do Not Work Inside Ranges
A range means "all values between two strings of the same length". Writing 100*..399* makes the system look for values that literally contain an asterisk, which normally matches nothing. Use 100000..399999 for a range, and use wildcards only with the Begins with ( 500* ), Ends with ( *500 ), and Is like ( *500* ) operators.
4. Seven Criteria per Line
Each grid line holds a maximum of seven criteria for a given segment. To add more, use Duplicate in the Segments and allowed values section, which copies the branch to a new line where the extra criteria can be entered.
5. Activation, Overlap Detection & the Draft/Active Trap
An account structure edit always happens on a draft ; the draft has no effect until activation. Activation is also when full validation runs.
Validate is not activation. The Validate button performs a limited check and can pass while overlapping criteria still exist. Full overlap detection only runs during activation, when the system builds every possible tree path.
Activation compares the draft against other structures' active versions , not their drafts. If two structures are in draft at the same time, the form shows you the drafts while activation silently checks the versions you can no longer see — the classic cause of an "impossible" overlap error.
Moving a value between structures needs two passes. To move main account 250 from AS2 to AS1, first remove it from AS2 and activate, then add it to AS1 and activate. Attempting both in one pass produces an overlap error because both structures briefly claim the value.
Tree Propagation
The grid is a flattened view of a tree, so a single row is a path from root to leaf. Changing a value on a shared left-hand segment updates every row that shares that branch. Four rows that all carry Business unit * will all change to 001 if you edit any one of them. To give one row a different value, copy the row, change the copy, and delete the original.