I have moving expenses carried forward from last year I could not claim, but can claim this year. In Part 4 this computes what gets entered. In box 27 the amount is < $1000, in box 28 you have to put in your eligible income (annoying side note: I have to compute this manually for some reason instead of TT figuring it out for me). The amount is >$10000. Box 29 is the allowable moving expenses which is the lesser of either 27 or 28, yet TT incorrectly enters enters a value of 0 (should be box 27). I suspect the S/W is incorrectly subtracting one from another, gets a negative number and puts in 0 instead. This is not correct, if box 28 is greater than 27 then 29 gets filled in with box 27, else it gets box 28. Also, box 30 (the carry forward) is set to 0.
Currently the only way to fix is to override, but that voids e-submission. Please fix in the next update.
Update, but first a rant:
As I have seen elsewhere in these groups there is absolutely no mechanism to report a bug and to have it tracked to it's completion. Either fixed, available in release X, or not a bug for reasons Y & Z. All you can do is post on these boards an pray somebody monitoring them has enough interest/bandwidth to investigate the posts and do something internally. Awful for a company as large as Intuit, but it's great for fault metrics since you don't have a customer-centric mechanism for tracking continuous improvement. But I digress...
I figured the only way to achieve an acknowledgement of the issue was to call. Surprisingly, I did not have to wait that long in the queue, however what ensued afterwards was extremely painful and unnecessary. First of all I want to say the person I had both times on the call was very courteous, patient, and genuinely interested in helping me. I wish all support staff I've had to deal with were as friendly. Unfortunately it appears the internal support mechanisms she had to deal with were less than helpful, and (IMO) downright condescending at times. It appears that there is a 1 hour limit phone support can spend at any one time and after the first hour my problem was not resolved, a call for the next day was scheduled. The following day I was called back and we pursued the problem for another hour to no avail. I was promised another call the following day and it never happened. I guess 2 hours is the limit for any one problem, and I still was unable to get it working.
What really gets me going is the "internal" group(s) she was corresponding with stated "there is no problem". Well, I beg to differ and if any internal "developer" had lifted a finger and tried a simple test it would have been immediately obvious there is a problem.
I can make the deduction work with a hack to work work around the BUG. If ANYBODY at Intuit is monitoring this open up a ticket and get it fixed.
If you have a moving expenses carry forward from previous TT will not allow the claim unless you override (and thus have to mail in your return). The BUG which needs fixing is that in order for TT to allow the claim the number in line 3 in PART 2 (in the same form) must be greater than 40 km. Yes, you have to tell TT that the distance you moved LAST YEAR (even though you did not actually move that year) must be greater than 40 kms. Only then will it process the carry over moving expense and claim it. This is obviously not correct and is a hack to work around the bug which will allow you to submit electronically. Note I have not tried to file the return yet, so there may be other issues...
To any Intuit support support staff monitoring: The proper implementation is to allow any value in line 24a to be claimed regardless of the result in line 3. It appears TT is using the result in line 26 or 27 conditioned by line 3 which is not correct. Carry forwards can be used at any time provided it is less than the Net Eli gable Income in line 28.
Sign In
Canada (English)
EN
