code # 95365 how to fix this?

[nerdboyjoe]

---

@CM1965 wrote:

That has to be an April Fools joke about the update not being ready till April 9th.  Any company that wants to remain in business would not be so delinquent in responding to user needs for something as important as filing income taxes.  I mean, it could only be a joke, right?

---

It’s no joke @CM1965 . Do you hear me laughing? Nope.

[Freddie44]

I just redid all my taxes with Wealthsimple and am getting the same result with box 68140 not populating for my spouse who has the Net Capital Loss.  It is populating for my return but I'm not in a Net Capital Loss position.

Both TT and WS have the same problem exactly.....non population of box 68140 when in a Net Capital Loss position. 

I'll try to contact WS tomorrow and see what they say and get back to you all.    

[sarahs3]

did you successfully netfile with wealthsimple?

[nerdboyjoe]

@sarahs3 i did. But even even you have an issue, I’m sure their tech support can’t do any worse than TurboTax’s.

[IslandRed]

I'm in the same boat as you.  I have prepared tax returns with both Turbotax and Wealthsimple.  Both have exactly the same amount of a refund.  I have a capital loss which creates a zero on line 68140 on the T936.  This happens for both Turbotax and Wealthsimple. 

NOW>>>>> If I remove the transaction creating the capital loss (remove it from the Scedule 3),  line 68140 then correctly populates with the total of the Box 21 on the T3's.   This also happens with Turbotax AND Wealthsimple.  

So if it happens with both, how can it be a Turbotax coding issue?  Damned if I know...

[sarahs3]

It looks like for me line 68150 should be populating a 1 but its populating the same number reported in 68140.

[nerdboyjoe]

@IslandRed as mentioned to another poster, I had a capital gain, not a loss, so maybe that’s why it worked for me in WS. Anyway, if there is a capital loss bug in both applications, I’ll bet you $20 (Canadian dollars!) 

that WS gets a fix out before TurboTax. Wanna try me? Contact both support teams about it tomorrow morning and see what happens.

[Marie92]

I called tonight and so far there is no fix.

[IslandRed]

I was just told by a support person at TT via Facebook chat that the error code has been fixed and that a release correcting the error will go out late next week...

[koshaughnessy]

It’s not unverified: