Dynamics 365 Finance 10.0.49: Fixed Assets Reporting Currency Adjustment Preview

What changes in version 10.0.49

Dynamics 365 Finance 10.0.49 adds a new preview feature named Fixed assets reporting currency adjustment. The capability is enabled through Feature management and introduces a process for fixed asset reporting currency adjustments that can be prepared, inspected, and posted.

In consultant terms, this means that reporting currency differences related to fixed assets no longer have to be treated only as an external reporting or manually calculated general ledger issue. The new process is intended to bring the calculation and posting of relevant adjustments into Dynamics 365 Finance, with a review stage before entries are committed.

The feature is marked as preview in the September 2026 release. Preview status is significant: it should be evaluated in a sandbox, and its suitability for production use must be checked against Microsoft’s preview-feature policies and the organization’s own change controls.

The business problem behind the feature

A Dynamics 365 Finance legal entity can maintain both an accounting currency and a reporting currency. Fixed asset transactions normally originate from operational events such as:

• Acquisitions and acquisition adjustments
• Depreciation
• Write-ups and write-downs
• Transfers or reclassifications
• Disposals
• General ledger adjustments associated with fixed assets

Where two currencies are maintained, fixed asset reporting can become difficult because asset values are accumulated over long periods. An asset’s acquisition, subsequent adjustments, depreciation, and disposal may occur on different dates and under different exchange rates.

This can produce a difference between:

1. The reporting currency value generated when individual transactions were originally posted.
2. The reporting currency value required for a later reporting date or accounting policy.

Before this feature, organizations could address such differences through processes outside the fixed asset workflow. Typical approaches included spreadsheet calculations, consolidation adjustments, or manually prepared general ledger journals. These methods can achieve the required financial result, but they also introduce practical weaknesses:

• The adjustment calculation may not be reproducible inside the ERP system.
• Reviewers must compare spreadsheet data with fixed asset and ledger balances.
• Manual journals can lose the connection to the underlying asset population.
• Account and financial-dimension selection may be inconsistent.
• Audit evidence is distributed across files, approvals, and journal attachments.
• Repeating the calculation at each month-end increases operational effort.

The 10.0.49 feature is an improvement because it establishes a system process with distinct generation, review, and posting stages. That separation should make the adjustment cycle easier to control than an immediate or purely manual posting.

What the feature does not yet tell us

The release note should not be read as a complete functional specification. In particular, it does not confirm the following details:

• Whether adjustments are calculated per asset, fixed asset book, value model, asset group, or ledger account.
• Which fixed asset transaction types participate in the calculation.
• Whether the process uses a closing rate, transaction-date rate, or another exchange rate rule.
• Which exchange rate type supplies the rate.
• Whether posted adjustments update fixed asset book values, general ledger balances only, or both.
• How financial dimensions are derived.
• Whether adjustments are automatically reversed in the next period.
• How prior adjustments are recognized when the process is run again.
• How disposed, suspended, split, or transferred assets are handled.
• Whether the process supports all posting layers and fiscal calendar scenarios.

These are assumptions to verify in a sandbox. They should be recorded as explicit test questions in the solution design or update assessment.

A particularly important question is whether the resulting entry is represented in the fixed asset subledger or only in the general ledger. The answer determines how reconciliation reports, asset statements, disposal calculations, and future adjustment runs should be interpreted.

Why the review stage matters

Currency adjustments can affect material balance sheet and profit-and-loss amounts. A proposal or review stage gives finance teams an opportunity to validate the result before posting.

A useful review should answer at least these questions:

• Is the selected legal entity correct?
• Is the adjustment date in the intended fiscal period?
• Is the asset population complete?
• Are excluded or disposed assets treated as expected?
• Does the exchange rate match the approved finance rate?
• Are balance sheet and offset accounts appropriate?
• Are reporting currency amounts directionally correct?
• Does the proposal duplicate an earlier adjustment?
• Can the total be reconciled to an independent calculation?

The release documentation does not specify which of these fields or controls are exposed by the preview interface. The checklist therefore describes the required control outcome, not confirmed screen behavior.

Who is affected

Finance and fixed asset roles

The main affected roles are likely to include:

• Fixed asset accountants, who maintain asset books, transactions, and depreciation processes.
• General ledger accountants, who reconcile accounting and reporting currency balances.
• Financial controllers, who approve period-end adjustments and review material currency effects.
• Group reporting teams, where reporting currency balances feed consolidation or management reporting.
• Internal and external auditors, who require evidence for the calculation, review, and posting.
• Dynamics 365 Finance functional consultants, who must assess setup, security, posting, and reconciliation effects.

Security administrators may also need to assess whether existing duties and privileges provide access to the new process. Microsoft’s short description does not confirm the delivered security artifacts, so this must be checked after deployment.

Processes

The feature can affect:

• Month-end and year-end fixed asset close
• Reporting currency reconciliation
• Fixed asset-to-ledger reconciliation
• Group reporting preparation
• Journal approval and posting controls
• Audit evidence retention
• Disposal and depreciation checks after an adjustment

The process owner should decide whether the adjustment is required monthly, quarterly, annually, or only for specific reporting events. That decision depends on accounting policy rather than the software feature alone.

Legal entities

The feature is primarily relevant to legal entities that have a reporting currency configured and hold fixed assets with balances that require currency adjustment.

It may have little practical relevance where:

• Accounting and reporting currencies are the same.
• The legal entity does not maintain fixed assets in Dynamics 365 Finance.
• Currency differences are intentionally handled only in a consolidation system.
• Group accounting policy does not require a separate fixed asset reporting currency adjustment.

Organizations should assess each legal entity independently. A process that is appropriate for one company may be unnecessary or inconsistent with policy in another.

What to do before the update

1. Document the current process

Identify how fixed asset reporting currency differences are handled today. Capture:

• Calculation files and data sources
• Exchange rates and rate types
• Journal names and ledger accounts
• Financial-dimension rules
• Approval responsibilities
• Reversal procedures
• Reconciliation reports

This baseline is needed to determine whether the new feature reproduces the intended result and actually removes manual work.

2. Identify representative test assets

Prepare a small but varied test population, including:

• A current-year acquisition
• An asset acquired in a prior year
• An asset with acquisition adjustments
• A fully depreciated asset
• A partially depreciated asset
• A disposed asset
• An asset with multiple financial dimensions
• An asset affected by a transfer or split, if used by the organization

Include at least two fiscal periods with different exchange rates.

3. Establish expected results independently

Create a controlled calculation outside the system using the organization’s approved accounting interpretation. The objective is not to preserve a spreadsheet process permanently, but to have an independent benchmark for testing.

4. Review configuration and data quality

Before enabling the feature, verify:

• Accounting and reporting currency setup
• Exchange rate types and available rates
• Fixed asset books and posting profiles
• Main account setup
• Financial dimensions on assets and source transactions
• Open and closed fiscal periods
• Existing manual reporting currency adjustment balances

Poor historical data or missing exchange rates may make the test result difficult to interpret.

What to test after the update

Enable the feature first in a non-production environment and run a controlled end-to-end test.

1. Generate an adjustment for a known asset population and period.
2. Compare the proposed amounts with the independent benchmark.
3. Review asset, book, account, date, currency, and dimension details exposed by the process.
4. Post the proposal in the sandbox.
5. Inspect the resulting voucher and ledger entries.
6. Reconcile accounting currency and reporting currency balances.
7. Review fixed asset reports to determine whether they include or exclude the adjustment.
8. Run depreciation after posting and check for unintended effects.
9. Test a disposal after an adjustment.
10. Run the adjustment process again to identify duplicate-prevention or incremental logic.
11. Test correction, cancellation, or reversal handling.
12. Confirm security access and segregation of duties.

Recommended adoption approach

Do not treat Feature management activation as the complete implementation. The functional process, accounting interpretation, and control ownership must also be agreed.

A practical adoption decision should require:

• Successful sandbox validation
• Documented calculation logic
• Controller approval of the accounting outcome
• Confirmed reconciliation procedures
• Tested security roles
• A decision on how prior manual adjustments will be handled
• Confirmation that preview use is acceptable under organizational policy

If the detailed behavior does not match the company’s accounting policy, retain the existing controlled process and reassess the feature after Microsoft provides fuller documentation or a generally available version.

References

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