Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Keep an eye out for upcoming NetSuite events, including meetups, workshops, and webinars. These sessions are a great way to connect with peers, learn from experts, and stay current on the latest NetSuite updates and best practices. Registration links are provided in each event.
SuiteWorld | October 25–28, 2026 | Las Vegas Where our community gets ready for what’s next!
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
What is causing the Fixed Asset Depreciation history schedule to stop before depreciation end date?
Hi There
I have an asset with the following set up:
I have tried toggling the depreciation active between 'true' and 'false' to trigger the generation of the depreciation schedule.
Every time the depreciation schedule is generated, it stops at 30/06/2023
The asset lifetime had been revised from 30 months to 60 months on 1/09/2022.
However, I don't believe that is the only thing affecting the calculation as pre-revaluation, the depreciation calculations stopped at 30/06/2022:
I have looked at Suiteanswers 98688 which suggests the 'last depreciation period' field being set incorrectly could be causing this. However, in this case, the value (4) appears to be correct.
What is causing this?
Tagged:
0