That's my problem as well. I'm in a net loss situation and line 68140 not populating with either Wealthsimple or TurboTax. If you find out anything, would definitely appreciate if you would post
MY EXACT PROBLEM AS WELL WITH BOTH SOFTWARES
Thank you to the user that posted neither WealthSimple nor TurboTax was working properly if in a capital loss scenario. I was about to rekey my information into WealthSimple, but apparently that would be a waste of time. Perhaps it’s not TurboTax that is at fault on this but rather the Canadian government, who has made capital gains changes so complicated that it has been difficult for the software companies to respond. Anyways, it has made for a lot of unwanted anxiety at a time when a lot of us are feeling great pressure. Hopefully the resolution comes through soon and things get back to normal.
@CM1965 @leop and others. I think I figured something out this morning from closely reading CRA's definition of error 95365 on this page and then examining both Chart A of form T936 and Schedule 3. Here is that definition:
There are entries for capital gains on T3 information slips and one of the following situations applies to your client’s return:
If that definition is up to date and CRA's Netfile validation code is actually following it precisely, then I see a problem with the validation code. The problem is, there is no mention of Line 17599 in that definition. Why does that matter?
If you look beside line 68140 in Chart A of form T936, it says "Enter the amount from box 21 of all 2024 T3 slips". Box 21 is the sum of boxes 52 and 53 on the T3. However, on schedule 3, boxes 52 and 53 are not summed into box 17600. Rather, the sum of all boxes 52 go into line 17599 and the sum of all boxes 53 go into line 17600.
That means the validation check is comparing apples with oranges. Specifically, line 68140 includes amounts from both boxes 52 and 53 whereas box 17600 includes amounts only from box 53. Note that as per point #1 of the error 95365 definition above, box 17600 and 68140 do not have to be equal. Rather line 17600 should not be greater than line 68140. That's why the rule passes for some people (like me) but not others (like the people who said they have some negative amounts in some of the box 52 and/or 53 entries).
I believe that both WealthSimple and TurboTax would be susceptible to this CRA bug. However, the problem can be expected to be more prevalent with TurboTax if you are splitting your T3's with your spouse. That's because the current version (as of today, April 2) of TurboTax is not splitting the capital gains amount between spouses, whereas WealthSimple is splitting it correctly (yes, I checked this). If you are single, or not splitting T3's with your spouse, then I would expect that the prevalence of error 95365 would be equal in both software applications.
To workaround the issue with CRA's validation not taking into account line 17599, one possible one that I can think of is to put the sum of box 52 and box 53 into box 53 and clear out box 52 on all your T3 slips, and make sure that it equals what is in box 21. The distinction between box 52 and 53 is now irrelevant because the government rolled back the change that would have made that distinction matter (Google that if you want to fact check it).
After doing the workaround but before you attempt another Netfile, make sure you closely examine the lines mentioned in the definition of error 95365 to make sure the rules are now being satisfied 100%. If not, then retrace your steps and try again. Read the definition closely!
I hope this helps.
It is not about Turbo Tax .
I am using TaxPrep for preparing personbal taxes, but QuickBooks for everything else and I am quite happy with them.
Problem with code #95365 occurs when you have 50/50 split between couuple (joint accounts), then if it's an odd number, tax program is rouding to lower or higher amount which results in discrepancy.
For example if a gain is $13, it should be $6.5 per couple, but on line Line 68140 in Form T936 shows $7.
The best solution is to increase for a dollar on T3 slip and make it a round number after 50/50 split.
That solves the problem and you'll be able to e-file the return.
My numbers are evenly split and it wont netfile. My wifes netfiled without error and everything is 50/50 so why does one work and not the other?? I called CRA today and after 1hour they said there was nothing wrong with my return and they could not find a solution. They have passed my issue up to the IT support to investigate why it is producing the 95365 error, when the conditions for the error are not met.
Thank you for the update, and we do understand your frustration. Rest assured, we are aware of this issue, and our development team is working on a resolution. Once it is resolved, we will update you in this thread. We appreciate your patience.
I thought the fix update was done yesterday. We need proper answer immediately
I have 66/34 split on T3 between me and my spouse. When I look at the forms, row 68140 in T936 is calculated correctly for me, but it is zero on my spouses return.
In schedule 3, rows 17599 and 17600 of my return, turbo tax did not calculate the split, it gave me the total amount, which is not correct. My spouses schedule 3 rows 17599 and 17600 are zero.
So, my return got rejected because schedule 3 capital gains do not match T936 capital gains.
The capital gains in schedule 3 is the total of rows 17599 and 17600, error 95365 does not state this.
i bet if you look at your wife’s Schedule 3 row 17599 and 17600, they are both zero. And further, you wife will not have a T936, because the turbotax software did not allocate her 50% of the T3 capital gains.
there are a many problems with the T3 processing which is why I’m waiting for the update was told was coming on April 8
Are you a BOT or real person? It would be nice if you gave an eta for the fix!
duaneanderson
Level 1
CM1965
Level 2
SandyB4
New Member
hometxgr
Level 1
hometxgr
Level 1
You have clicked a link to a site outside of the TurboTax Community. By clicking "Continue", you will leave the Community and be taken to that site instead.