- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
Is there a bug with the 2018 Individual ProSeries program calculations of taxable State tax refunds from 2017 received in 2018? My program (fully updated as of 2/6/19) reflects the refund as non-taxable when I think it should be taxable. Part II, Line 5 is showing $-0- when on my 2017 Sched A Line 5 reflected $15,608 of State Income Taxes paid and deducted. Is there a problem with the program or am I not reading something correctly?
Best Answer Click here
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
This issue was fixed several weeks ago. If you had transferred your files prior to fix, you would need to delete and re-transfer your clients. If you've worked on any clients prior, you'll need to re-transfer the ones you have not. Either that or manually make change on the worksheet.
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
Development is looking into this issue.
If the Income Taxes box is not checked on Line C of the State and Local Income Tax Refund Worksheet and it should have been then you would want to check that.
If you are sure the full prior year refund should be taxable this year you can skip making the manual adjustment and just check the box below line 4 for "Use this worksheet to complete taxable refund amount? - If no, skip this Smart Worksheet. Total refund from Line 1 column (b) will be reported as income."
**Mark the post that answers your question by clicking on "Accept as solution"
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
This has caused a major problem for tax preparers and has harmed our clients who have had returns filed with erroneous state tax refund information (tax refunds that should have been taxable and were not reported as taxable). How can we log a complaint with Intuit as to how this was handled and who will be paying our clients interest and penalty that may be charged when we have to amend returns to report this income that Proseries erroneously missed?
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
Slava Ukraini!
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
♪♫•*¨*•.¸¸♥Lisa♥¸¸.•*¨*•♫♪
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
Slava Ukraini!
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
I'd think that would be the person whose signature is at the bottom of the 1040/8879.
That said, I absolutely agree that the Intuit communication was sorely lacking on this. The November Alert said it would be fixed in December but to my recollection this was not fixed until January. I don't know when it was fixed because there was no Alert informing folks 1) that it was fixed and 2) the steps they would need to take to ameliorate the problem.
It should not have happened to begin with. Somehow Intuit has a nasty habit of breaking things that worked perfectly well in prior years. Hey, stuff happens. But they're a big enough company that they should have a well-staffed QC department to keep the stuff that happens behind closed doors rather than releasing it to their customers. They were clearly aware of the problem in November, yet it took them well over a month to fix it.
The only "fix" was to the transfer-from-prior-year process, nothing was done regarding data files that had already been transferred. While doing so certainly would have been difficult (arguably impossible under the current programming), it would not have been difficult to add a diagnostic (if transfer date < 1/xx/19 AND state refund wks box C2 is checked then trigger diagnostic warning). Another alternative, there are already at least 3 check boxes I have to check on clients *every* year to "verify" that the information transferred over correctly. Direct deposit info, ID info and the state ID number on every W-2 and 1099-R. Those checkboxes are mandatory and flag a red error if they are not checked. So they could have easily added a checkbox after the fact for the preparer to verify that the state tax refund transferred correctly.
Rick
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content

♪♫•*¨*•.¸¸♥Lisa♥¸¸.•*¨*•♫♪
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
That, however, does NOT absolve the tax preparer of his/her responsibility for getting the numbers correct.