3.4 Advanced Rules & Advanced Rule Structures
Key Takeaways
- 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).
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
MainAccountsegment 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
DepartmentandCostCenter. - 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.
A retail company wants to require a 'StoreLocation' dimension only when posting to Revenue accounts (400000..499999) where the BusinessUnit is 'RETAIL'. For all other BusinessUnits (such as 'ONLINE' or 'CORP'), StoreLocation must not be displayed or required. How should this be configured?
A ledger account structure already uses all 11 available segments, and the business now needs a Grant dimension to appear on grant-funded expense accounts only. What is the maximum number of segments the resulting ledger account can contain, and how is the Grant segment added?