Dynamics Community Forum Thread Details

Fixed Assets Short/Long Year Calendar Using Percentages

Customer is a retail chain that uses the Short/Long Year FA Calendar and percentages for years that <> 365 days. This is typical for retail stores to have odd calendars. They wind up having thousands of assets that are fully depreciated with a NBV. The fix is normally to change the FA LTD amount to = the cost of the asset to bring NBV to zero. With thousands of assets, this is not an easy fix. They've been using a mail merge macro that would update the assets. They do not want to use this workaround and also are concerned that forcing the NBV to zero during the last year of the asset’s life has possibly understated the asset’s true depreciation in previous years.

Customer is looking for permanent solution whether that’s another workaround in FA OR some type of customization.

Does anyone know of other retail customers or otherwise having a similar issue and how they have resolved? If not within GP, can anyone recommend any outside FA applications that can manage these calculations that could be then be integrated into GP as a JE?

Thank you,

Nancy Hogan

Categories:

Microsoft Dynamics GP

Hey Nancy,

This is a tough question without being able to see how the Asset is setup and how your calendar is defined.

More often, this should not be leaving a Netbook Value. The long/short year should still allow you to fully depreciate the Asset. It could be an issue with how the Asset is Setup or the calendar long/short percentage is set to.

There was also an issue I believe that was never fixed if the Long/Short year was used for every single year. I don’t recall the issue off and you would need to create a case with Microsoft to find out this information.

Manually updating the LTD amounts should create an entry that can be pushed to the GL so it should not cause any balance issues. However, you do not mention if the Remaining year/days is 0 or if this still has remaining life that is to be depreciated and why the Netbook value is not zero.

My suggestion here is to create a case with Microsoft to have them review the Asset in question, the calendar and determine why it is actually not fully depreciating the Asset as it should still fully depreciate when using the long/short year. This will also help determine if you are running into a Product Issue with the Long/Short year and perhaps they have a workaround for this. This way no customizations are needed and can verify the setup is correct.

I hope this helps!

Thank you!

Brandon
Functional Consultant
Enavate - Microsoft Dynamics 365 Implementation & Support | Cloud ERP Consultant (enavate.com)

Quick Links

Leaderboard