Study guide
3.4 Advanced Rules & Advanced Rule Structures
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.4 Advanced Rules & Advanced Rule Structures
Key Takeaways Explain This Topic AI
Advanced rules add extra dimension segments only when a filter condition on the account structure is met, extending the total to a maximum of 16 segments (Microsoft Learn, Account structures overview).
You can attach as many advanced rules as you want to an account structure; when several apply, Dynamics 365 Finance evaluates them in alphabetical order by rule name.
Segments added by an advanced rule are always appended after the segments of the parent account structure — they cannot be interleaved.
Budgeting does not use advanced rules, so any dimension you plan to budget against must appear in the account structure itself.
More than roughly 20 advanced rules on a single structure degrades activation performance (Microsoft Learn, Best practices for account structures).
Last updated: August 2026
3.4 Advanced Rules & Advanced Rule Structures
Quick Summary: Advanced rules make a financial dimension appear as a segment only under defined conditions, such as requiring a Customer segment on revenue accounts. They extend an account structure past its 11-segment ceiling to a documented maximum of 16 total segments, at a real cost in activation performance.
1. Advanced Rules & Advanced Rule Structures
While primary account structures govern universal dimension combinations, business scenarios often require conditional dimension requirements that apply only under specific circumstances.
Problem Scenario
An enterprise requires the Department and CostCenter dimensions on all expense accounts ( 600000..699999 ). However, whenever an employee incurs travel expenses ( MainAccount 601500 ), the system must also require an Employee dimension. Adding Employee directly to the primary account structure would force an empty segment across all other 500+ expense accounts, degrading usability.
The Solution: Advanced Rules
Advanced Rules extend an account structure by attaching an Advanced Rule Structure when specified filter criteria are met. +-----------------------------------------------------------------------------+
- | ADVANCED RULE ARCHITECTURE |
- +-----------------------------------------------------------------------------+
- | PRIMARY ACCOUNT STRUCTURE: P&L Expenses |
- | - Segments: MainAccount (600000..699999) -> BusinessUnit -> Department |
- | |
- | ADVANCED RULE CRITERIA: "RequireEmployeeOnTravel" |
- | - Condition: Where MainAccount == 601500 AND Department == "SALES" |
- | |
- | ATTACHED ADVANCED RULE STRUCTURE: "EmpStructure" |
- | - Segment: Employee (Required: No blank allowed) |
- | |
- | POSTING RESULT: |
- | - Account 601100 (Rent): Enforces MainAccount-BU-Department |
- | - Account 601500 (Travel): Enforces MainAccount-BU-Department-Employee |
- +-----------------------------------------------------------------------------+
- Rules for Advanced Rule Structures
Path : Configured under General ledger > Chart of accounts > Structures > Advanced rule structures .
No MainAccount Segment : Advanced rule structures contain only financial dimensions; the MainAccount segment is prohibited because it is already defined in the primary structure.
Capacity : An advanced rules extend the ledger account to a documented maximum of 16 total segments , counting the account structure's own segments.
Linking : Advanced rules are created directly on the parent account structure ( Configure account structures > Advanced rules action pane button ), specifying the activating criteria filter.
2. Account Structure Design Decision Matrix
Design Approach Best Suited For Advantages Disadvantages / Risks
Single Monolithic Structure Small businesses with uniform dimension requirements across all accounts Single point of maintenance; simple initial setup Complex wildcard grids; poor performance; blanks allowed everywhere
Modular Structures (By Account Type) Mid-size to enterprise organizations (Balance Sheet vs Revenue vs Expense) Clean validation; enforces dimensions only where needed; high performance Multiple structures to maintain; requires strict Main Account range governance
Primary Structures + Advanced Rules Enterprises with specialized compliance, project, or audit requirements Keeps primary structures lean; dynamically enforces rare dimensions Additional configuration complexity; must manage both rule types
3. Segment Capacity: How Advanced Rules Extend an Account Structure
The single most-tested number in this area is the segment ceiling. Microsoft documents it in two parts:
Container Documented maximum What counts
Account structure 11 segments One MainAccount segment plus up to 10 financial dimensions.
Account structure + advanced rules 16 segments total The 11 structure segments plus the extra segments contributed by advanced rule structures.
Once a structure already holds 11 segments, the Add segment button is greyed out. The only supported way to surface an additional dimension on a ledger account is an advanced rule, and even then the combined total is capped at 16 segments. Treat any exam option that claims an advanced rule gives you "unlimited" segments, or that an advanced rule structure can itself hold another 10 dimensions, as wrong.
Building an Advanced Rule
Open General ledger > Chart of accounts > Structures > Configure account structures and select the parent structure.
Put the structure into Edit (draft) mode, then choose Advanced rules .
Define the rule criteria — the condition that makes the extra segments appear (for example, Main account is between 400000 and 499999 ).
Attach one or more advanced rule structures , each of which lists the extra segments and their allowed values. Rule structures are built the same way as account structures and can be shared across several rules .
Activate the account structure together with its rules. Activation, not Validate , is what performs full overlap detection.
Behaviour Rules That Decide Exam Answers
Ordering is alphabetical. When more than one advanced rule qualifies, Dynamics 365 Finance applies them in alphabetical order of the rule name. Naming rules 10- , 20- , 30- is the practical way to control sequence.
Segments are appended, never interleaved. Segments contributed by a rule always appear after every segment of the parent account structure. You cannot slot a rule segment between Department and CostCenter .
Budgeting ignores advanced rules. Budget register entries and budget control evaluate only the account structure. If the business must budget on a dimension, that dimension has to live in the account structure itself — putting it in an advanced rule silently removes it from budgeting.
Blank values are still validated. If either the account structure or an applicable advanced rule disallows a blank segment, a ledger account that leaves it blank fails validation.
Performance Guardrail
Microsoft's account structure best-practice guidance warns that more than roughly 20 advanced rules on a single structure causes extended AOS processing time during activation with no corresponding SQL activity. The same guidance warns against the anti-pattern of putting an asterisk on every account structure segment and relying entirely on advanced rules for validation: it is hard to maintain, error-prone, and slow. Consolidate rule criteria into the account structure whenever the dimension is genuinely required for that account range.