Perhaps this should be posted in the USA forum, but it is a bug so I’ll post it here. I finally took the time to fully chase down what I thought I had discovered as a bug in the DB1/SL depreciation calculation. The details are fairly lengthy so I will not repeat them here. The result is that the asset is fully depreciated during the year prior to the year in which full depreciation should take place. The problem was reported to (and acknowledged by) NSUS today. I have not yet received any information as to how long it will take to get it fixed. As best I can tell, the bug has been in all recent versions of NF. Anyone who would needs the details, please email me.
I seem to have the answer to this. NSUS replied that the problem lie not in the calculation, but in the fact that I was depreciating beyond dates set up in the Accounting Period table. For depreciation to work correctly, it must rely on the accounting period dates. You should have accounting years defined as far out as your latest Ending Depreciation Date. If you do this, it works as it should. I have placed in the hopper a suggestion that an edit be added to base NF to warn of this condition. In actuality, except in the testing mode I was in, you will be depreciating in the current fiscal year, which will already be set up. It is interesting that the depreciation projection, which goes into the future, calculates correctly even without all needed future fiscal years defined…