Fixed Assets depreciation overstated or negative Net Book Value

We are coming up on the time of the year where we see an influx of cases around Fixed Assets with a problem of overstated depreciation, or assets with a negative book value.

This issue is usually caused by either closing the Fixed Asset year before all assets are depreciated to the last day of the year or a combination of running the Fixed Asset year end close too early and then flipping the year back in the Fixed Asset Book setup. When this occurs, there are a few options dependent upon the situation.

Option 1:
If the Year End close in the year with the overstated depreciation has not been run, a Reset Year can be run against all the assets.

Option 2:
If the year has been closed in which the depreciation was overstated, they can run a Reset Life against all the assets.

In both Option 1 or 2 the following article can be helpful:

861544 - How to reset the life of an asset or of a group of assets in Fixed Asset Management in Microsoft Dynamics GP;EN-US;861544

We should also, recommend that they test the outcome in a test company first per KB 871973 and have their financial people check the numbers.

871973 How to set up a test company that has a copy of live company data by using SQL Server 7.0, SQL Server 2000, or SQL Server 2005;EN-US;871973

Option 3:
In some cases, running a Reset Life or even a Reset Year may not be desirable. This is particularly true for customers that may have recently started using the Fixed Asset module and added in assets with depreciation already on them. In this scenario, the ‘Reset’ will most likely not calculate the depreciation the same as their previous Fixed Asset system.

If neither Option 1 or 2 are acceptable, Microsoft Support can resolve this through a data fixing service.

In all of these situations, we should reinforce the proper method for closing the Fixed Asset year. If the problem was caused or potentially caused by changing the year value in the Book setup, I also recommend that they restrict access to the Fixed Asset Book setup window as flipping the year value is not supported past setup.

865653 The year-end closing procedures for the Fixed Asset Management module in Microsoft Dynamics GP and in Microsoft Great Plains;EN-US;865653


Ken H.

Comments (4)

  1. Hi Ken,

    We have found for 4-5 assets depreciation is overstated. Users says they have not changed any Depreciation Sensitive field.

    Assets life was 5 yrs-Place in Service Date : 02/28/2007 Last Depreciate to Date: 02/27/2012.

    I don’t know why only for few assets System Calculated Negative Depreciation?  

    Please need help to troubleshoot issue.

    Waiting for your reply.



  2. Ken Hubbard says:


    Blog comments are not used to provide support assistance. I would recommend opening a support case or submit your question via a forum post:…/32.aspx

    Thank you,


  3. Sandip says:


    Support request is opened in GP Community. Here is link…/142506.aspx

    Can you please help me to troubleshoot this issue? On April some assets are going to be fully depreciate and when we did Depreciation ( In Test Co) it is giving me negative value in 'Asset Net book value'

    Waiting for your reply.



  4. Ken Hubbard says:

    Hi Sandip,

    You can see my comments in your post. The solution remains as suggested in this blog however.


    Ken Hubbard

Skip to main content