Form 1116 efile reject code F1116-012

[Kathi_at_Intuit]

Hi Everyone and thank you @Just-Lisa-Now- for the tag.  We’re checking on this rejection and appreciate your patience while our team reviews the details. We’ve shared this thread with the appropriate group for further investigation to help identify what’s causing the issue.

Once we have an update or additional guidance, we’ll post back here to keep you informed. 

Thank you for bringing this to our attention and for being part of the community!

[JMad]

While I can appreciate you trying to look into this matter, this has been a problem for SEVERAL years and that has been the response every year.  This occurs EVERY October when we are at the height of our craziness.  As I mentioned previously, we pay SO much money for this software that refuses to correct itself.  PLEASE find a work around as quickly as possible.  

[mrusso]

For what it is worth, JMAD's solution appears to work for the F1116-13 reject codes (moving line 3b to line 3a).  however, F1116-12 reject code (Form 1116, Line 2) still appears even after entering statement data as the reject code suggests.  there does not appear to be a workaround for this code.

Also, this has been an ongoing issue for the past three years!

[JMad]

Agreed.  I was able to clear the F1116-13 reject code but still trying to figure out how to clear the F1116-12 code myself.  I will update if i can find a work around.  

Thank you mrusso for your response.

[JMad]

‎09-20-2024 04:18 AM

This worked for us:

found this response from Rob-W on 9/20/24 as his workaround last year for line 2.   I believe we did the same thing last year.  Going to give it a shot.   Again--not the right way to be filing and Proseries NEEDS to address but if it works so be it.

We entered the Form 1116, Line 2 "Expenses definitely related" on Line 5, "Losses from foreign sources", instead.  The Line 6 totals remain the same.  To cover ourselves, we add the following note to both Line 2 and Line 5 and tick the box, "Print this note as part of the tax return for filing":

These are definitely related expenses that normally are entered on line 2. Trouble is, there is a ProSeries tax software glitch associated with the line 2 required statement that prevents efiling when an amount is entered on line 2.  Therefore the expenses are entered on line 5 as a workaround to permit efiling.

We hope this is helpful, and we hope ProSeries is able to sort out this issue with the IRS soon and fix it in the software.

[beanctr72]

Yes, this workaround did work for mine this year. 

[mrusso]

Thank you JMAD and Rob W.  this work around worked!!!!  moving the amount from line 2 to line 5 did the trick.  Thanks for the support.  Just wish ProSeries would provide some assistance other than draining my wallet.

Thanks again!

[JMad]

and don't you love having to go back into all of your returns to correct these errors?  I have some very large tax returns and this is time I don't have right now.  (not to mention it isn't accurate).  You would think that with so many people calling technical support for YEARS they would determine this is a problem that needs to be rectified.  I tried calling several times after tax season last year to try and get this escalated to no resolve.  But they will make sure to pull our LARGE payment for the software!