3.1 Custom & Entity-Backed Financial Dimensions
Key Takeaways
- Custom financial dimensions hold an independent value list maintained inside General ledger; entity-backed dimensions draw their values from an operational table such as Customers, Vendors, Projects, or Workers.
- Entity-backed dimension values appear automatically when the underlying master record is created — you never add those values by hand.
- Dimension value masks (#, &, ?, !) enforce an alphanumeric format on custom dimension values at entry and import time.
- A balancing financial dimension set on the Ledger page generates automatic inter-unit due-to/due-from entries so each dimension value balances to zero on every voucher.
3.1 Custom & Entity-Backed Financial Dimensions
In Microsoft Dynamics 365 Finance, the General Ledger relies on a multi-segmented account model. Rather than creating thousands of discrete main accounts to track operations across departments, cost centers, business units, or projects—a practice known as "chart of accounts inflation"—organizations utilize Financial Dimensions. Financial dimensions serve as data qualifiers that attach to ledger transactions, providing rich operational context for financial analysis, management reporting, and statutory compliance.
1. Architectural Foundations: Custom vs. Entity-Backed Dimensions
When designing financial dimensions (General ledger > Chart of accounts > Dimensions > Financial dimensions), a functional consultant must choose between two distinct dimension types:
+-----------------------------------------------------------------------------+
| FINANCIAL DIMENSION TYPES |
+-----------------------------------------------------------------------------+
| 1. Custom Financial Dimensions |
| - Defined independently within General Ledger |
| - Managed manually or imported via Data Management Framework (DMF) |
| - Supports Dimension Value Masks for strict format enforcement |
| |
| 2. Entity-Backed Financial Dimensions |
| - Bound directly to system entities (Departments, Vendors, Projects) |
| - Dimension values auto-generated when master records are created |
| - Lifecycle managed directly within the parent operational module |
+-----------------------------------------------------------------------------+
Custom Financial Dimensions
- Definition: A custom dimension is an independent list of values created and maintained strictly within General Ledger.
- Configuration: Select
<Custom dimension>in the Use values from dropdown. - Use Cases: Lines of business, sales channels, market segments, strategic initiatives, or regulatory classifications that do not correspond to an existing system entity.
- Value Management: Values are added manually via the Financial dimension values action pane button or imported using the Financial dimension values data entity.
Entity-Backed Financial Dimensions
- Definition: An entity-backed dimension draws its values directly from an operational master data table.
- Available Entities: Business units, Departments, Cost centers, Customers, Vendors, Items (Released products), Projects, Fixed assets, Workers, Agreements, and Legal entities.
- Synchronization Mechanics: When a user creates a new record in an operational module (e.g., creating Customer
US-004in Accounts Receivable or Fixed AssetFA-0012in Fixed Assets), Dynamics 365 Finance automatically inserts a corresponding dimension value into the financial dimension table. You do not need to manually add values to the dimension. - Governance: If a master record is renamed or blocked in the subledger, its status is reflected in the financial dimension values lookup.
Dimension Value Masks
For custom dimensions, organizations often require standard alphanumeric formatting (e.g., cost centers must follow the format CC-### or regional codes must match REG-AA-###). Dynamics 365 Finance provides Dimension value masks on the financial dimension definition form.
| Mask Character | Allowed Input Type | Description |
|---|---|---|
# | Digit only (0–9) | Requires a numeric character at this position. |
& | Letter only (A–Z, a–z) | Requires an alphabetic character at this position. |
? | Letter or Digit (Alphanumeric) | Allows any single letter or digit. |
! | Uppercase letter only | Forces capitalization of alphabetic characters. |
| Constant / Literal | Characters (e.g., -, /, CC) | Fixed text that automatically formats the input. |
Consultant Note: Dimension value masks are validated only upon manual entry or during DMF import validation; they do not apply retroactively to existing dimension values.
2. Balancing Financial Dimensions (Inter-Unit Accounting)
Many multinational organizations require balanced balance sheets at a sub-entity level (e.g., by Business Unit or Fund) to satisfy statutory or segmental reporting requirements (such as IFRS 8 or US GAAP ASC 280). When a single transaction or journal entry involves multiple business units, the debits and credits for an individual business unit may not balance, even though the voucher balances as a whole.
To resolve this, Dynamics 365 Finance supports Balancing Financial Dimensions (General ledger > Ledger setup > Ledger):
+-----------------------------------------------------------------------------+
| INTER-UNIT BALANCING ARCHITECTURE |
+-----------------------------------------------------------------------------+
| Single Ledger Parameter: Balancing financial dimension = [BusinessUnit] |
| |
| Journal Line 1: Debit Expense (MainAccount 601100, BU: 001) $1,000 |
| Journal Line 2: Credit Cash (MainAccount 110100, BU: 002) $1,000 |
| |
| Automated Postings Generated by Ledger Engine: |
| Auto Entry 1: Credit Interunit Payable (Account 219900, BU: 001) $1,000 |
| Auto Entry 2: Debit Interunit Receivable(Account 139900, BU: 002)$1,000|
| |
| Result: BU 001 Net Balance = $0.00 | BU 002 Net Balance = $0.00 |
+-----------------------------------------------------------------------------+
Rules for Balancing Dimensions
- Single Dimension Limit: Only one financial dimension per legal entity can be selected as the balancing financial dimension on the Ledger record.
- Automatic Posting Accounts: The posting engine relies on accounts configured in General ledger > Posting setup > Accounts for automatic transactions:
Interunit - debit(Due from other units / Interunit receivable)Interunit - credit(Due to other units / Interunit payable)
- Posting Behavior: During posting, if the sum of debits does not equal the sum of credits for any distinct value of the balancing dimension in a voucher, the system generates balancing debit and credit entries using the designated interunit accounts, stamped with the respective balancing dimension values.
An organization creates a new financial dimension named 'VendorDivision' and sets 'Use values from' to 'Vendors'. A purchasing agent creates a new vendor record (US-109) in Accounts Payable. What must the General Ledger team do before US-109 can be used as a financial dimension value on journal entries?
A multinational company requires balanced balance sheets for each Business Unit. During general journal posting, an expense line of $5,000 for Business Unit 100 is credited against a Cash account stamped with Business Unit 200. What configuration is mandatory for this transaction to post successfully?