You’re offline. This is a read only version of the page.
Announcements
3,494
Hi:
We were testing Calculate Depreciation for each month in the first half of 2022 and comparing with depreciation calculations in a spreadsheet that show what amounts should result.
For January and February, we thought that depreciation figures from BC "tied" with those in the spreadsheet. But, then, we saw that one of the FA Posting Groups had been coded to an amortization account rather than a depreciation account.
So, I adjusted that Posting Group to post to the correct depreciation account.
Then, we ran Calculate Depreciation for March. It still posted some depreciation to the wrong account (i.e., the amortization account)!!!
We closed out, came back in, and ran depreciation for April. Then, depreciation posted to the proper account and not to amortization.
But, we then found that depreciation figures for each group were off from those of the spreadsheet.
This inaccuracy continued to get worse, when we kept running Calculate Depreciation for subsequent months.
Again, aside from finding that some depreciation in BC contained amortization due to wrong FA Posting Group coding, depreciation was accurate in the beginning. It just somehow got worse.
Some assets have many decimal places for years of life, while others have no decimal places.
Could that be causing the wild discrepancies? Is there a fix?
Thanks!
John
Hi Kim:
This is testing. So, it's okay.
I'm trying to figure out why depreciation got "more off" as "time went on" (i.e., as an additional month of depreciation was run).
Any ideas?
John
John, the depreciation calculation is not based on your fa posting group. What depreciation method are you using?
I do agreed that you need to cancel the previously posted depreciation entries and redo....suggest checking the entries before you post....
Hello John
you need to cancel the wrong entries and recreate again with the correct account.
If you still have a problem with decimal, is better report a support case because we had an issue with it in the past and we have a PTE to correct wrong decimals
Hope this helps
#1
André Arnaud de Cal...
294,095
Super User 2025 Season 1
#2
Martin Dráb
232,866
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (
