Skip to main content
June 3, 2019
Question

Feedback - TurboTax made a mistake on my Oregon Non-Resident tax return. On form OR-ASC-N/P TT tried to show my Federal pension as subtraction even though non-taxable.

  • June 3, 2019
  • 2 replies
  • 0 views

Here's what the letter from Oregon Revenue says, in pertinent part:

"We adjusted or denied your federal pension subtraction (code 307). Your subtraction for federal pension income is limited to the taxable amount included in the Oregon column." (Full text attached.)

Since the taxable amount in the Oregon column was zero, the subtraction should have been zero. However, TT included the entire amount as a subtraction.

2 replies

Critter
June 3, 2019

 

If you purchased Audit Defense for your tax return, call Tax Resources, Inc. at (877)-829-9695, or report your notice on their web site at http://intuit.taxaudit.com/. Do not contact the IRS. Let Tax Resources contact them for you.

This is the membership email you should have gotten:  https://ttlc.intuit.com/questions/1901569-when-will-i-get-my-audit-defense-membership-kit

Also read the member agreement at this website -https://turbotax.intuit.com/corp/auditdefense.jsp


If you did not purchase Audit Defense:


TurboTax has a special phone number for help with IRS tax letters, which will be easier than going through regular Customer Support.   At the page below, click on the blue button that says "Get Help from TurboTax Support".  Then it will ask you what tax year is your letter.  Then it will ask you what the letter concerns. Then it will show you the phone number during posted business hours.

https://support.turbotax.intuit.com/irs-notice/audit-support/

 

mgnewmanAuthor
June 3, 2019
I did not purchase audit defense. I do not need help with the letter. The letter from Oregon Revenue is correct. The tax return is wrong. I just want Turbo Tax to fix their software so that it won't make the same mistake next year. If I don't hear from TurboTax that they will fix this, then I won't pay them to do my Oregon tax return next year. That's why I headed my question with "Feedback".
March 29, 2025

It's 2025 and this error still has not been fixed.