Choose tags for the right information

Financial dimensions support structured accounting and reporting requirements. Tags support transaction-level context. Both can help analysis, but tags do not replace account structures or the validation rules attached to financial dimensions.

Use tags for information that needs to travel with an accounting entry without becoming part of the ledger account structure. Define clear ownership and naming conventions so that the fields remain useful rather than becoming a second description field.

Set up and activate a tag

Define the delimiter in General ledger parameters before setting up tags. Then create the tag, choose its value type and activate it in the relevant legal entity. Labels must follow the application’s naming rules.

The financial tag delimiter is configured in General ledger parameters.
The financial tag delimiter is configured in General ledger parameters.
Example tags with different value types and sources.
Example tags with different value types and sources.

Text allows free entry. List and Custom list provide suggested values but do not, by themselves, enforce membership. Finance 10.0.44 introduced Fixed list and Fixed custom list for restricted value entry. Choose the type that matches the actual control requirement.

Default values with a rule

Enable Financial tag defaulting rules and configure the document entry point, transaction level and target tag. A condition builder or supported Power Fx formula determines the default value.

Activating tags makes them available for the relevant transaction experience.
Activating tags makes them available for the relevant transaction experience.

The rule can use available transaction fields, but support differs by document and application version. Check which fields and entry points are available instead of assuming that every tag-enabled document supports the same defaulting behaviour.

Test the record lifecycle

A default is not a one-time design decision. Test record creation, field changes and saving, together with the overwrite setting. Header-to-line copying and user-defined rules can execute at different points.

  • Does the rule populate the right target and transaction level?
  • What happens when a user enters a different value?
  • Does the rule replace an existing value only when intended?
  • Do existing lines change when the header changes?
  • Does the tag reach the expected posted accounting entries?

Part 2 applies these questions to a Region tag on a sales order. Keep the test focused on the full document lifecycle, not only the first value visible on the header.

Further reading

For current feature availability, prerequisites and detailed configuration, refer to Microsoft Learn.

Screenshots and scenarios are illustrative. Interface labels and available features can vary by application version and environment.