Why sign in to the Community?

  • Submit a question
  • Check your notifications
Sign in to the Community or Sign in to TurboTax and start working on your taxes
Level 3
posted Jan 16, 2024 11:15:31 AM

Form 4562 not transferring prior year depreciation - Is that intentional programming of the software or is this a glitch?

Folks,

I have been using TT Business desktop since 2020 tax year.  I am reviewing form 4562 and have noticed that the column for prior year depreciation is not completely filled.  That is, the prior year depreciation value of my work vans is populated with the correct value (see yellow highlighted cells).  The prior year depreciation of my computers and printers does not show the total depreciation over the years (see green highlighted cells).

 

Is that intentional programming of the software or is this a glitch?

 

0 3 595
1 Best answer
Level 3
Jan 19, 2024 2:18:53 PM

Hello @MarilynG1 , thank you for this response.  I was on the phone for over 2 hours with Turbo Tax Desktop technical support.  They admitted that this is a flaw in the programming and that they will fix it.  It is not a failure of entering data in my 2017 return, as you suggested.

3 Replies
Level 3
Jan 17, 2024 9:44:30 AM

Is there an answer for this?

Expert Alumni
Jan 19, 2024 1:38:01 PM

I would advise looking at your 2017 return where you initially added the assets.  Unless you deducted their cost as an expense, you should have an amount in 'Prior Depreciation'  and 'Accumulated Depreciation', not just 'Current Depreciation' in your returns from 2018 going forward.  

 

Since we can't see your return in this forum, you may want to enlist the aid of TurboTax Live to help you with this issue.

 

Here's a TurboTax Community discussion of a similar issue; with a workaround. 

 

 

 

 

 

 

Level 3
Jan 19, 2024 2:18:53 PM

Hello @MarilynG1 , thank you for this response.  I was on the phone for over 2 hours with Turbo Tax Desktop technical support.  They admitted that this is a flaw in the programming and that they will fix it.  It is not a failure of entering data in my 2017 return, as you suggested.