3.2 Financial Tags: Limits, Storage & Ledger Settlement Use

3.2 Financial Tags: Limits, Storage & Ledger Settlement Use

Quick Summary: Financial tags let an organization record up to 20 user-defined fields on accounting entries without inflating the chart of accounts. They trade validation, defaulting, and budget control for near-zero performance cost, which makes them the right tool for high-cardinality transactional references.

---

1. Financial Tags (FinTags): Architecture & Benefits

Prior to the introduction of Financial Tags, organizations frequently created financial dimensions to track operational and transaction-level details such as Purchase Order Numbers, Work Orders, Asset IDs, Delivery Slips, or External Reference Numbers. This practice led to severe database degradation.

The Problem: Dimension Combination Bloat

Traditional financial dimensions generate unique combination records in the DimensionAttributeValueCombination (DAVC) and DimensionAttributeValueSet (DAVS) hash tables. Every time a unique combination of main account and dimension values is used, a new hash key is generated. Storing high-cardinality values (e.g., 500,000 unique PO numbers) causes:

• Massive index fragmentation and table bloat in DAVC/DAVS.
• Slow General Ledger posting throughput.
• Degradation of financial reporting query performance.

The Solution: Financial Tags (FinTags)

Financial Tags (General ledger > Chart of accounts > Dimensions > Financial tags) provide lightweight, transaction-level tracking without creating records in DAVC or DAVS.

Financial Tag Delimiters

When viewing tag combinations across reporting grids or data entities, tags are concatenated using a designated delimiter (e.g., -, ~, |). Delimiters are specified during financial tag setup to ensure clean parsing across external BI tools and integrations.

---

2. Configuration Walkthrough: Step-by-Step

+-----------------------------------------------------------------------------+
|              FINANCIAL DIMENSION & TAG SETUP WORKFLOW                       |
+-----------------------------------------------------------------------------+
|  [1. Define Dimensions]  --> [2. Configure Values]  --> [3. Set Ledger]     |
|  - GL > Dimensions          - Entity or Custom         - Balancing Dim      |
|  - Select 'Use values from' - Set Active Dates         - Auto Accounts      |
|                                                                             |
|  [4. Create FinTags]     --> [5. Assign to Trans]   --> [6. Post & Edit]    |
|  - GL > Financial tags      - Enter on GL/Subledger    - Edit post-posting  |
|  - Tag Type: Text/List      - Subledger propagation    - Verify in GL lines |
+-----------------------------------------------------------------------------+

Step 1: Create an Entity-Backed Dimension (Department)

1. Navigate to General ledger > Chart of accounts > Dimensions > Financial dimensions.
2. Click New. In the Use values from field, select Departments.
3. In the Dimension name field, enter Department.
4. Click Activate on the action pane to register the dimension schema.

Step 2: Create a Custom Dimension with Value Mask (SalesChannel)

1. In the same form, click New.
2. In Use values from, select < Custom dimension >.
3. In Dimension name, enter SalesChannel.
4. In the Mask field under the Value mask fast tab, enter SC-###.
5. Click Dimension values in the action pane and create values: SC-001 (Retail), SC-002 (Direct Online), SC-003 (Wholesale).

Step 3: Configure Financial Tags for Operational Tracking

1. Navigate to General ledger > Chart of accounts > Dimensions > Financial tags.
2. Click New.
3. Enter Tag name: TrackingNumber, Value type: Text.
4. Click New to create a second tag: Tag name: CostPool, Value type: List.
5. Select CostPool, click Tag values, and add: POOL_A, POOL_B, POOL_C.
6. In Financial tag configuration, set the Tag delimiter to |.

3. Tag Capacity, Enablement & Where Tags Are Supported

Each legal entity can define up to 20 financial tags. The tags are configured at General ledger > Chart of accounts > Dimensions > Financial tags, and the feature itself must first be turned on in the Feature management workspace. Tags are legal-entity specific, so the same 20-slot allowance exists separately in every company; the Financial tag configuration and Financial tags custom list value data entities let you replicate an identical setup across entities quickly.

Value Types and the Absence of Validation

A tag is defined with a value type of Text, List, or Custom list. The value type only shapes the lookup shown to the user — it does not enforce anything. Even for a List or Custom list tag, a user can type a value that is not in the list and the transaction will post. There is no way to require a tag value. If the business needs enforced, validated coding, the answer on the exam is always a financial dimension, never a tag.

Where Tags Are Available

Tag uptake expands with each release rather than arriving all at once. Tags started in the General journal and Global general journal, and later releases extended them to further journals and documents. Financial tags for procurement documents require Dynamics 365 Finance version 10.0.49 or later and the Enable financial tags for purchase order invoicing feature. When a case study describes tagging that is not available on a given document type, the correct answer is usually to check the release and the feature flag rather than to reconfigure the tag.

The Ledger Settlement Payoff

Because the tag value lands directly on the accounting entry, ledger settlement can match on it. A PurchaseOrderNumber tag lets the goods-received/invoice-received clearing account settle automatically by purchase order, which is precisely the scenario tags were designed for: a very high-cardinality reference (hundreds of thousands of distinct values) that would cripple the dimension combination table if it were modelled as a financial dimension.

Exam trap: If you disable the Financial tags feature after values have been entered, the database keeps the values but they disappear from every form and inquiry. Disabling is not the same as deleting.