Try this workaround: enter 100% ownership at the top and then half of all values into boxes for each person. (I also only entered capital gains in box 53, using the same value as line 21, half the total, instead of dividing the time periods.).
Then the values for line 68140 on T936 were correct and agreed with Schedule 3 line 17600, and try to file.
We are aware of this issue, and our development team is working on a resolution. We appreciate your patience.
Thank you.
Manually splitting all T3's is an option I considered but not sure why I have to manually do anything in an $80 software package for Taxes???? Especially for a basic calculation in a core function.
When will the software error be fixed?
@rsslack exactly!!! Manually splitting is too tedious, especially if you have several T3 slips. That’s why we bought this software in the first place. I think the development team consists of a man and his dog, and the dog is doing the QA. How else can you explain the glacial speed of releasing a fix for this? Terrible epic fail this year, TurboTax!
Yet another day has passed with no fix for this T3 splitting issue in the desktop version of TurboTax. What is taking so long for a seemingly simple math fix in the code? It’s unbelievable. I’m so frustrated with TurboTax. Give us an ETA.
@rsslack We can understand your frustration. We are aware of this issue, and our development team is working on a resolution. We are hoping this can be resolved quickly. Once it is resolved, we will update you in this thread. We appreciate your patience.
Is there a known bug list somewhere? I spent hours trying to figure out what was going on before I realised it was a bug in Turbo tax. I know errors happen, but we shouldn't have to guess about known errors.
@dtaylor1199 I can't find any known bug list, but this bug is definitely known! LOL! Cue the stock train wreck footage!
We are aware of this issue, and our development team is working on a resolution. Currently we don't have any ETA. Once it is resolved, we will update you in this thread. We appreciate your patience.
@Kp3838 We are aware of this issue; rest assured, our development team is working on a resolution. Once it is resolved, we will update you in this thread. We appreciate your patience.