AltaRed

Agreed. As I understand it, the data file Netfiled to CRA does not contain it anyway.

Agreed. Going back to the first post, no interest would be declared in 2022. It will all be declared in the 2023 tax year.

You can if you wish but UFile may not accept it this way. In which case just show 100% on your son's return. CRA may come back with a query on that when they process the NOA, upon which case you will need to send CRA a letter with the explanation. The question is.... why is your SIN on that GIC investment to begin with? Try to get that changed with your financial institution for next year.

No. I wish UFile would tell us what each update fixed. It is bizarre for a software company not to publish a record of revisions and why. May have to stop using this software if they are so secretive about what changes they make.

When you first load UFile, do you not see the files you can open in the dialog box? UFile knows which folder you saved the *.u20 files and they would show in the dropdown dialog box.

Go to the tab of Tax Return... between the Review and the Netfile tabs. You will see options to save PDF and print.

I've seen at least a few instances on financial forums where people have brought up that issue. It must be a set of somewhat unique circumstances. What I have advised people to do is as you suggest. Let Maxback optimize and then do a case with zero split to be sure. If the zero split works out better, then one needs to iterate between 0 and Max to find out where the optimum is. I now do a zero split case just in case..... Regardless, UFile needs to re-visit and QA the algorithms for those particular circumstances.

All is well. That happened to me too (and I think it was that way in 2019 too). UFile needs to make a programming change to avoid that screen re-appearing. It should go straight to the confirmation page.

Concur. I would just file the correct 2020 version and leave it at that. There's been no obvious conscious effort to evade/avoid correct reporting.

In the T5008 input form.... in Boxes 11, 13, 13-21 as appropriate. The sum of cost or book value goes in Box 20 and the proceeds of disposition go in Box 21. Recommendation: In the future for keeping track of adjusted cost base data it would be easier to use something like https://www.adjustedcostbase.ca/ for this data, tracking it as you go day to day, week to week.

No, you don't have to use the T5008 entries at all. I never use them. I enter my own acquisition (ACB) data and disposition proceeds in Schedule 3 which is the third line in the Investment Income and Expenses sub-section. T5008 data is prone to error and misuse. By definition, those Schedule 3 entries will use the same disposition data as the T5008 EXCEPT for any transactions done in USD, in which those values have to be multiplied by the forex rate in effect on the dates of the transactions, i.e. the forex rate on the date of acquisition, and the forex rate on the date of disposition.

Ass I have posted in another section, it has been historically correct (or commonplace) to allocate contributions made in the first 60 days of the year, e.g. Jan 1-Feb 28 2021 apply, in whole or in part, to the prior tax year 2020, or to the current tax year. That may no longer be the case (to be confirmed) but in this instance, just do a manual override as noted by TheTaxSmith to limit how much of the 2021 contribution applies to the 2020 tax year. I did this on a regular basis for some time (and ignored the UFile warning). At one time TurboTax (or as it was known before as QuickTax I think that I used in the 1990's) had an option to allocate the split. I have no idea what other software does today. In any case, it seems prudent for some research to be done to clarify whether the rules have changed at some point in time. It has been years since I made a RRSP contribution.

UFile Maxback contains some flaws that have been exposed in the past, and reported by some individuals, but apparently they have has not been fixed. It is supposed to iterate for maximum benefit (least combined tax for a couple) but something is busted internally. The issue may be related to the lower income spouse losing more in tax credits, such as age amount (for seniors) or medical deduction threshold, than the higher income spouse benefits in lower income tax paid. I don't know where the bust is and UFile needs to work on it. My best suggestion is to run the results two ways: 1) let Maxback decide, and 2) shut pension income splitting off as you have done. If the result is that 1) is better, run with it. If 2) is better, chances are there is an optimum somewhere in between 0% pension income splitting and up to 50% pension income splitting. What that means is DON'T let Maxback decide and run your own manual iterations at perhaps 10% increments between 0% and 50% to find a better optimum. Iterate as you wish to fine tune it to the nearest percentage point if you have nothing better than time and/or are motivated to find the last dollar.

I have finally solved the mystery, at least for me. It was my synchronizing software, specifically Dropbox, that caused this message. When I paused Dropbox synchronization, UFile saved without this error message. This 'error message' may also apply to other synchronizing software such as One Drive or Google Drive. Try pausing and see if that works.

In surfing various threads, I found this thread from a few years ago. The culprit appears to be Windows Defender. I will try that solution the next time I am into Ufile. Tried this. Both by allowing the app in Protected Folder Access and by turning Protected Folder Access off. Neither approach worked. I do think the issue has to do with Windows Security and/or Windows Defender though. A vendor IT rep needs to show up and respond to these issues.

Most of the time I still get this message despite no other non-system app being open. Occasionally I do not but rarely. That all said, I have been inputting data and it seems like Auto Save is working because the data is still there when I open that File again. I guess the bigger question is whether this thing will calculate and save the actual tax return when it is time to Netfile. I would have thought there would have been some response from the vendor by now to this topic. Clearly something is amiss here and the conflict has to be a Win10 system executable of sorts.

Ufile 2020 installed fine and it brought forward a .u19 file for conversion to .u20. However, every time I try to Save the .u20 file after entering data, I get a dialog box that says: Failed to Save The tax file you are trying to save is locked by another application What is going on given there is no other application that can possibly be accessing and using this file extension?