AI, in your work.

Two fixes with accounting implications

Microsoft merged two fixed asset fixes for Microsoft Dynamics 365 Business Central into BCApps on October 27. Pull request #13171 provides evidence of their incorporation into the code, which is separate from delivery of an update.

The posting group determines which general ledger accounts asset transactions use. Microsoft's documentation explains that its configuration covers acquisition, depreciation and disposal. Changing it therefore warrants reviewing the accounting effect as well as checking whether the field accepts the new value.

When a posting group change is blocked

The W1 fixed asset depreciation book code adds a check against the stored record. It blocks the change when all these conditions apply:

• A last acquisition cost date exists.
• The stored posting group is nonblank and differs from the new value.
• Allow Changes in Depr. Fields is disabled on the depreciation book.

What changes for cancellations

In the W1 cancellation code, if document number retrieval returns blank, the number is taken from the last line in the same journal template and batch. This logic appears in both the fixed asset journal and the fixed asset G/L journal.

One limitation follows from reading the code: if that last line also lacks a number, the fallback will still return blank. The fix does not guarantee valid numbering regardless of the journal's existing contents.

Scope, version and test evidence

The request is assigned to milestone 30.0, described as Business Central online 2027 release wave 1, with no due date. That planning information does not establish a shipped build or availability in a particular installation.

GitHub shows 176 checks passed when the request was merged. The author states that the new tests were not run locally. The check count alone does not establish that every functional scenario ran successfully.

The commit includes depreciation book changes in W1, DACH, FR, GB and RU; cancellation changes in W1, FR and RU; and tests in W1, ES, RU and CZ. CZ receives only cancellation tests: according to the description, its localization already applies a stricter posting group restriction. This file coverage does not confirm commercial availability by country.

Three scenarios for preparing a check

The following examples are synthetic and have not been run. They provide a basis for designing checks in a test environment whose build includes the change.

Nexo's interpretation: separate configuration from accounting correction

The commit states that enabling the setting still permits a posting group change but does not transfer existing balances. Our interpretation is that the functional team should handle the field edit and any required reclassification separately.

To correct an erroneous acquisition, Microsoft documents using Cancel FA Entries, followed by the correct posting; it also warns that Reverse Transactions cannot be used for these entries. Practical review should preserve traceability between the acquisition, cancellation and replacement posting.