Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Fixed Asset Issue
Finance | Project Operations, Human Resources, ...
Answered

Fixed Asset Issue

(0) ShareShare
ReportReport
Posted on by Jozy 385

Hello Community,

Hope all healthy!

Actually I am depreciating one asset but it is showing 10 times more then the other months. You can see below snap.

GP-Fixed-Asset.jpeg

Thanks in Advance

Categories:
Microsoft Dynamics GP
  • Jozy Profile Picture
    Jozy 385 on at
    RE: Fixed Asset Issue

    Hi  Andrea,

    There is one thing is left can you please guide me some assets still showing the depreciation rate is not correctly it is showing 15% which was our last rate. Snap is attached.

    Correct Number should be is ( 8.038.59 )

    WhatsApp-Image-2021_2D00_07_2D00_12-at-1.00.38-AM.jpeg

    Thanks.

     

  • Jozy Profile Picture
    Jozy 385 on at
    RE: Fixed Asset Issue

    Thank you Andrea.,:)

  • Verified answer
    Andrea Melroe Profile Picture
    Andrea Melroe 3,437 on at
    RE: Fixed Asset Issue

    Hi Jozy,

    This is Andrea, and I will assist with your question today.

    I’ve seen this issue crop up when users update the ‘current fiscal year’ in the FA40200 on the backend to allow depreciation in a ‘new’ year without closing the ‘current’ FA year. Here’s more detail around what I think happened:

    1. At the end of your last FA year in Fixed Assets, the user did not close the FA year.
    2. Instead, he/she flipped the ‘Current Fiscal Year’ forward to the ‘next’ year for the CORPORATE book on backend (you should not do this) and depreciated without having closed the previous year.
    3. Then, after depreciating 10 periods in the ‘new’ year, the user flipped the ‘Current Fiscal Year’ back to the previous year and performed the FA year end closing at that time.
    4. Here’s what happened when the user depreciated for those 10 periods in the ‘new’ year prior to closing the previous year:
      • The YTD depreciation field in the Asset Book window was increased by the appropriate amount of depreciation each time the user depreciated (2083.36 * 10 = 2083.60 – almost the exact amount of overstated depreciation).
    5. Here’s what happened when the user flipped the year back to the previous year and closed the year:
      • The YTD depreciation field in the Asset Book window was zeroed out – this happens as part of the year end close process.
    6. As such, the following occurred:
      • All assets show correct periodic depreciation amounts in the Financial Detail Inquiry window.
      • However, the YTD depreciation field in the Asset Book window became understated by 10 periods worth of depreciation.
    7. When asset C10181 got to the last period in the new year: GP looked at the YTD depreciation field and saw that the total YTD depreciation was not equal to the ‘Yearly Depreciation Rate’ for the asset. As such, GP made up for the understated depreciation in that last period.

    I talk about this scenario in our Fixed Assets Year End Blog:

    https://community.dynamics.com/gp/b/dynamicsgp/archive/2018/11/27/microsoft-dynamics-gp-year-end-update-2018-fixed-assets

     pastedimage1625780773503v1.png

     

    To fix this problem you’ll need to test doing a ‘Reset the Year’ on all affected assets – I recommend doing this in a Test Company with a copy of live data:

    1. Click Transactions, point to Fixed Assets, click Select Assets, and then click New Group.
    2. Name the group, and then click OK.
    3. Under Current Groups, click the newly created asset group, click to select the assets (all assets) for which you want to reset the year, and then click OK.
    4. Click Transactions, point to Fixed Assets, and then click Mass Change.
    5. Select the newly created asset group ID, click the Book tab, select the book ID, select Reset Year, and then click Apply Changes.
    6. In the following message, click OK: Are you sure you want to apply changes to group (New_Group_Name)
    7. Close the window.
    8. Verify depreciation amounts, YTD, LTD, NBV amounts are now accurate.

    I hope this helps!

    Andrea Melroe | Microsoft Dynamics GP

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,214 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans