Why Fixed asset Reclassification Posting Works Without Provision Reserve Account in USMF ?

(5) Share

Report

Posted on by Sohaib Cheema

49,664 Super User 2026 Season 1

Does anyone know why the asset reclassification posting works without any issues in USMF (demo data), even though no posting accounts are set up for 'Provision for Reverse'?

The posting completes successfully without any errors.

However, on another system (which is not using demo data and is set up as a U.K. company), the posting fails and asks for the missing accounts in the Posting Profile.

I suspect that the 'Provision for Reverse' step is being skipped in USMF because it’s a U.S.-based company. But I haven’t been able to find any setting or checkbox that confirms this behavior.

Before I start debugging, I wanted to ask if anyone with experience in Fixed Assets can confirm if this is expected or if there’s a specific setup that controls it.

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (1)

Answers (1)

Verified answer

Sohaib Cheema 49,664 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Figured it out.

This occurs when you have a record listed in the posting profile but no main account specified (see the picture below).

So, in this situation (a row is specified but no main account is mentioned), if you try to reclassify an asset, the system will display the following error message:

This behavior is a bit strange from Microsoft standard code, considering the fact that it doesn’t matter which asset you are trying to reclassify. Every asset can have its own asset books, its own asset group, and its own asset posting accounts.

However, the system doesn't check this properly. Regardless of which row is missing a main account, it throws an error (as shown in the picture below).

I am running a Reclassification for a fixed asset that belongs to the Office group. This group of assets has nothing to do with other asset groups or other asset books.

However, just because there is a row or record in the posting profile without a main account specified, the system throws an error. As you can see from the posting setup(on given next picture), that row without Main Account does not belongs to the Office asset group (or the asset itself which is OFFICE-000001)

Long story Short, the asset reclassification process fails with an error if there’s any posting profile record missing a main account, even if that record doesn’t apply to the asset or asset’s group. This happens because the system checks all rows regardless of the asset group, to find if there is a row with empty Main Account. The solution is to ensure every posting profile record has a main account specified, or Microsoft needs to improve the system to ignore irrelevant rows during check(that occur before posting).

3 people found this reply helpful.

Was this reply helpful? Yes No