Dynamics 365 Finance 10.0.49: Reporting Currency Handling for Fixed Asset Splits

Overview

Microsoft Dynamics 365 Finance 10.0.49, listed for September 2026, introduces an enhancement called Reporting currency handling for fixed asset splits. It is an extension of the existing fixed asset split process and must be enabled through Feature management.

The enhancement is relevant when a legal entity maintains fixed asset balances in both:

• The legal entity’s accounting currency.
• A configured reporting currency.

When an asset is split, part of its value is transferred to a newly created asset. Before this enhancement, the reporting currency side of that operation could lose the exchange rate context associated with the original asset. This could produce reporting currency values that did not divide as consistently as the corresponding accounting currency values.

Version 10.0.49 changes that handling by retaining the relevant exchange rate information from the source asset during the split.

What changes in 10.0.49

The existing fixed asset split remains the business process: one asset is divided so that a portion of its value is assigned to another asset. The enhancement concerns how Dynamics 365 Finance determines the reporting currency values generated by that process.

With the feature enabled, the split uses exchange rate information associated with the original fixed asset transaction context instead of handling the resulting reporting currency amounts without that context. The intended result is that the source and new assets retain a more consistent relationship between accounting currency and reporting currency.

In consultant terms, the system should preserve the currency basis of the value being divided. It should not treat the transferred portion as though it were an unrelated amount requiring a new currency interpretation.

This matters because fixed asset balances are often historical. An acquisition may have been posted months or years before the split, at an exchange rate that differs significantly from the current rate.

Why this is an improvement

A fixed asset split is primarily a reclassification of existing value. It does not normally represent a new external acquisition or disposal. From that perspective, the reporting currency amount moved to the new asset should remain connected to the reporting currency valuation already recorded for the original asset.

If that connection is not retained, several practical issues can arise:

• The reporting currency proportion may differ from the accounting currency split proportion.
• The combined reporting currency balance of the two assets may not reconcile cleanly to the source balance before the split.
• Fixed asset reports may require manual explanation or adjustment.
• Controllers may see currency differences even though the split did not create a new economic event.
• Reconciliation between fixed asset subledger balances and general ledger balances can become more difficult.

The enhancement removes this pain point by carrying the source exchange rate context into the split calculation. This should make the result more predictable and reduce the need for manual reporting currency corrections.

Illustrative accounting scenario

Assume an asset has the following balances immediately before a split:

• Accounting currency balance: 100,000
• Reporting currency balance: 92,000
• Split percentage: 30 percent

A conceptually consistent result would allocate approximately:

The important control is not only the value assigned to the new asset. It is also whether the combined post-split reporting currency value reconciles to the pre-split value, subject to legitimate currency rounding.

This table is an acceptance-testing example, not a statement of the exact posting algorithm. The actual result can depend on the asset’s books, transaction history, split parameters, currency precision and applicable rounding rules.

The pain point in the previous behaviour

Before this enhancement, exchange rate details relevant to reporting currency were not consistently retained as part of the split. Consequently, the reporting currency amount on the resulting asset transactions could diverge from the historical currency relationship of the source asset.

This was most visible where:

• Accounting and reporting currencies had materially different exchange rates.
• The original asset was acquired under an older exchange rate.
• The split occurred long after acquisition.
• Assets contained several transaction types or adjustments.
• Finance teams reconciled balances independently in both currencies.

A difference discovered after posting could require investigation across the asset book, fixed asset transactions, vouchers and general ledger balances. Even when the monetary difference was small, proving why it occurred could consume significant time during period-end or audit work.

Who is affected

Business roles

The enhancement is most relevant to:

• Fixed asset accountants who create and validate asset splits.
• General ledger accountants who reconcile subledger and ledger balances.
• Financial controllers responsible for reporting currency statements.
• Finance solution architects who design currency and fixed asset processes.
• Auditors or internal control teams reviewing asset movements.
• Application administrators responsible for feature activation.

Processes

Review the feature if the organization uses any of the following processes:

• Splitting assets by quantity, organizational ownership or physical component.
• Reclassifying part of an existing asset into a separate asset record.
• Reporting fixed asset balances in a secondary currency.
• Reconciling fixed asset subledger values in both accounting and reporting currencies.
• Producing group or management reports from reporting currency amounts.

Legal entities

The most directly affected legal entities are those that have a reporting currency configured and actively perform fixed asset splits.

Legal entities without a reporting currency are unlikely to obtain a material accounting benefit from this specific enhancement. However, they should still include a basic split regression test if the feature is enabled globally in their environment.

The feature’s scope across companies, and whether activation can be controlled separately for each legal entity, should be confirmed in the target version. Feature management behaviour can differ by feature.

What to do before the update

1. Identify relevant legal entities

Create an inventory of legal entities that meet both conditions:

1. A reporting currency is configured.
2. Fixed asset splits are used or may be used.

Prioritize entities with high asset volumes, volatile currency pairs or strict reporting currency reconciliation requirements.

2. Capture baseline split results

In a current-version test environment, execute representative asset splits and retain:

• Source asset balances before the split.
• Split parameters and percentage or quantity.
• New asset balances after the split.
• Accounting currency and reporting currency transaction amounts.
• Generated vouchers.
• Relevant fixed asset and general ledger reports.

This baseline helps demonstrate the practical effect of the new feature after the environment is updated.

3. Prepare a test matrix

Include more than one simple acquisition. Useful scenarios include:

• A fully undepreciated asset.
• A partially depreciated asset.
• An asset acquired in an earlier fiscal period.
• An asset with acquisition adjustments.
• A split that creates currency rounding.
• Assets using different books, where applicable.

Treatment of depreciation, adjustments and other transaction types is not fully described in the release note. Their inclusion in the improved exchange rate handling is therefore an assumption to verify.

Activation and post-update testing

The capability is delivered through Feature management rather than being described as automatically mandatory.

Search for Reporting currency handling for fixed asset splits and review the feature information available in the updated environment. Confirm whether Microsoft marks it as preview, optional, enabled by default or mandatory in that build before deciding on the production activation date.

After activation in a sandbox:

1. Repeat the baseline split scenarios.
2. Compare accounting currency amounts before and after the split.
3. Compare reporting currency amounts before and after the split.
4. Check the source asset and newly created asset separately.
5. Reconcile their combined balances to the original asset balance.
6. Inspect generated fixed asset transactions and ledger vouchers.
7. Confirm rounding differences are within the expected currency precision.
8. Run the fixed asset and general ledger reconciliation reports used at period-end.

Testing should also confirm that normal asset split controls, approvals and posting profiles remain unaffected.

Data and deployment considerations

There is no indication in the brief release description that enabling the feature recalculates historical asset splits. The prudent assumption is that it changes future split processing only. Verify this in a sandbox and through the feature details supplied with version 10.0.49.

Do not enable the feature in production solely on the basis that it improves currency consistency. First document:

• The tested asset scenarios.
• Expected rounding tolerances.
• Reconciliation evidence.
• Any differences from the previous result.
• The intended activation date.
• The rollback or incident process if unexpected postings occur.

If existing assets already contain unexplained reporting currency differences from earlier splits, treat their correction as a separate accounting and data-remediation exercise. Do not assume that feature activation will repair them.

Consultant assessment

This is a focused enhancement, but it addresses a valid accounting control issue. A fixed asset split should divide existing value without unintentionally changing its historical reporting currency basis.

Organizations with no reporting currency or very few asset splits may see little operational impact. For multinational or Swiss-based entities using a reporting currency for group reporting, the improvement is more significant. It should reduce reconciliation effort and make split results easier to explain.

The key implementation task is not configuration complexity. It is proving, with representative asset histories, that the reporting currency allocation is consistent across all fixed asset transaction patterns used by the organization.

References

• Microsoft Learn: What’s new or changed in Dynamics 365 Finance version 10.0.49