Microsoft Dynamics 365 Business Central Self-Help Place

If you run Calculate Depreciation for a month, then run it again before posting, Business Central will create the same lines a second time. It does not warn you. Post that batch and you have depreciated twice. This one catches people at month end, and I have explained it enough times now that it deserves a post. What is actually happening Calculate Depreciation does not look at your journal. It looks at the Last Depreciation Date on the Fixed Asset Depreciation Book. That date only updates when you post . Not when you calculate. So the sequence goes like this: You run Calculate Depreciation until 30 April. Lines appear in the Fixed Asset G/L Journal. Something else comes up and you leave the lines sitting there, unposted. A few days later you run Calculate Depreciation until 30 April again. Business Central checks Last Depreciation Date, sees that nothing has been posted, and calculates April all over again. Now you have two sets of April lines in the same journal. ...

Just migrated to Business Central and the monthly depreciation doesn't match your schedule? In most cases BC isn't wrong. The accumulated depreciation migrated at cut-off was higher or lower than it should have been, and BC is correcting it over the asset's remaining life. Quick answer: BC's straight-line method doesn't simply carry on your fixed monthly amount. Each time depreciation runs, it takes the asset's current net book value and spreads it evenly over the time left until the Depreciation Ending Date . If the migrated asset was under-depreciated, BC charges more each month to catch up. If it was over-depreciated, BC charges less. How BC calculates it Depreciation = (Book Value − Salvage Value) × Depreciation Days ÷ Remaining Depreciation Days In plain words: what's left to depreciate, divided by the time left . This makes sure the asset is fully depreciated on its Depreciation Ending Date, even if the opening balance was off. Example ...