T3(SUPP) error after entering T5008 slips

[Stagingtt]

I am using TT2025 Canada Desktop.

I have entered 4 T5008 slips in the program and when I look at the T3(SUPP) form the number of shares sold is 100 times higher than what i entered.  I have checked all 4 T5008 entries.  When i put in 40 shares the T3(SUPP) form shows 4000.  I don see any decimal place or anything like that.  Why is this happening?

[Stagingtt]

Typed too quickly.  Obviously I mean the S3(SUPP) form and not T3(SUPP)

[TurboTax_Susan]

The forms are still not finalized, but there will be an update released before tomorrow's NETFILE opening, so that might contain a fix for this issue.  

The number of securities isn't used in the calculation, though, at least not on the S3 (SUPP).

[Stagingtt]

Thank You.  I shall check back after the next update.  Yes, the proceeds, cost and Cap Gain figures are correct.  As long as the CRA doesn't dive deep into the number of shares and flag incorrect share prices 🙃

[Stagingtt]

The problem with the S3(SUPP) form is still there after the latest TT update.  The shares sold column is still 100 times higher than it should be.  Yes, the proceeds, cost basis and cap gain figures are correct but after dealing with the CRA’s idiosyncrasies for over 40 years I know that any noticeable change in pattern year over year is what raises the flag with them to dig deeper.  If they cross check current prices with say BCE as an example it will look as if the share price was only 36 cents instead of 36 dollars.  This could cause them to request more detail about the transactions.  While the actual capital gains are correct this reporting issue on the S3(SUPP) form should be corrected soon so that people can file knowing they won’t be flagged for a reassessment.

[TurboTax_Susan · Accepted solution]

@Stagingtt The CRA has the information about the number of shares sold directly on your T5008 slips, so if they need to cross reference, they will get the information from there.  

I will pass this issue onto the product development team. 

[Stagingtt]

Thanks for that reply.  That now makes sense to me that they will get their info from the T5008 slips and not the summary.

[SteveM-Tax]

Agree that the correct "Quantity of Securities" that is used by the CRA is taken from the information entered into the TurboTax T5008 Slip, however, the information in the TurboTax Schedule 3 Supplemental Statement is still incorrect in TurboTax. 

I have all the latest updates currently released and Schedule 3 Supplemental Statement is still incorrect.   

The "# of shares" in S3(SUPP) is 100 X the "Quantity of Securities" entered into the T5008 which would be correct is this field was "Lots" but this is not the correct definition of this field when transferred to the S3 (SUPP). 

Should be a quick fix.    Has the TurboTax Product Development Team responded? 

Thanks, Steve 

[SteveM-Tax]

PC Download Version - As a follow-up to my original post, I checked TurboTax 2024 to see if this was a new bug introduced in TurboTax 2025 and this same bug is also in TurboTax 2024 (e.g. multiplying Quantity of Shares on the T5008 form by 100 when displaying the # of shares on the S3(SUPP) form).

TurboTax 2023 is correct and transfers the Quantity of Shares exactly as entered into # of shares on the S3(SUPP) TurboTax form so it looks like this bug was first introduced in TurboTax 2024.

For large numbers of trade transactions,  the S3(SUPP) is useful and much easier to review/proof read the T5008 entries than scrolling 3 entries at a time within the small T5008 window within TurboTax.  The T5008 slip from your Financial Institution is not very useful for final verification since the ACB is rarely accurate (for a number of reasons as acknowledged by the financial institution) and these entries won't match what is being submitted to the CRA for USD T5008 entries since multiple conversion rates are often required. 

I realize the Capital Gain/Loss calculations are still correct according to  the T5008 form input, however, to avoid confusion for those who do check the S3 (SUPP), it should be fixed.  

Steve 

[TurboTax_Susan]

@SteveM-Tax 

Our product development team is working on this issue, and it should be resolved in a future update.