Idea description

In Dynamics 365 Finance, financial tags are documented to follow the same defaulting logic as financial dimensions for source documents, based on the Values used for summary account parameter in General ledger parameters.

However, in purchase-related flows, a functional gap exists:

When a product receipt is posted, the Purchase Accrual (GRNI) accounting entry does not receive financial tag values, even when:

• Financial tags are entered on the purchase order header and/or lines, and
• Values used for summary account is set to Source document.

Because the accrual posting does not carry a financial tag, the invoice reversal reuses the original accrual entry and therefore also cannot receive a tag later. Additionally, the Vendor balance posting on the invoice voucher does not receive a financial tag in purchase accrual–related scenarios, even though the tag exists on the purchase order header and the parameter is set to Source document.

This behavior has been confirmed and documented as a current limitation, but it is not obvious from the existing documentation, which describes that for source documents:

• Summary account tag values should default from the document header or accounting distributions, following the same logic as financial dimensions.

From a customer perspective, this creates an inconsistency:

• Financial dimensions flow correctly for these postings.
• Financial tags flow correctly for other purchase‑related posting types (for example, cost postings).
• Financial tags do not flow for Purchase Accrual (GRNI) and related Vendor balance postings, even though they originate from the same source document.

Business impact

Customers cannot reliably use financial tags to:

• Track open GRNI balances at the general ledger level
• Perform automated GRNI reconciliation and ledger settlement
• Identify which product receipts have been invoiced versus which remain outstanding

This results in additional manual work, reduced transparency, and limits adoption of financial tags as an alternative to financial dimensions for operational tracking.

Requested enhancement

Extend financial tag support so that:

• Purchase Accrual (GRNI) postings created at product receipt can carry financial tag values derived from the source document (header or distributions), and
• Vendor balance postings in purchase accrual–related invoice flows can also receive financial tags when Source document is selected.

At minimum, clearly align system behavior with documentation expectations or enhance documentation to explicitly call out this limitation per posting type.