Re: eFile Error: Form 1099-R, 'PayerEIN' must match data in the e-File database.

tccpg289

I double checked all 1099-R and they are correct.

It could be related to the taxable refund (Arizona).

It is for a 1040, and I have already tried to eFile twice. How many attempts do I get?

What other consideration are there to consider before eFiling? Is this a known issue?

PhoebeRoberts

You get an infinite number of attempts! Any chance you've got an 8 that looks like a 3, or a 6 that looks like an 8, or a 5 that looks like an 8? You might be able to call the E-file help desk to see if they have any suggestions.

The e-file reject tells you which 1099-R is the problematic one. What's the payor name on that 1099R?

George4Tacks

Is there a separate AZ EIN? Did you enter that number? Is there a phone number on the 1099R? If so, call that number for help to get the number correctly. IRS is not a help source for this issue. You are in the right place to get help.

Answers are easy. Questions are hard!

tccpg289

Are you positive it is unlimited?

I have read 5 attempts in other articles. Would like confirmation.

PhoebeRoberts

I know for sure that neither Lacerte nor the IRS has any such limitation. I find no documentation saying that ProConnect does - what are you seeing?

(If you're looking at something like this - https://www.taxact.com/support/313/2024/irs-limit-on-electronically-filed-tax-returns?hideLayout=Fal... - what it says is that consumers, as opposed to professionals, can only submit 5 separate e-filed 1040s. If you're preparing more than 5 returns, and you want to e-file all of them, you have to get an EFIN and a PTIN.)

View solution in original post

George4Tacks

Based on @PhoebeRoberts new insight. @tccpg289 Do you have an EFIN recorded with ProConnect?

Answers are easy. Questions are hard!

tccpg289

Yes, I do indeed have an EFIN and PTIN, so I would presume that means I am not subject to any eFile limitations?

Intuit_Kallana

There are no efile limitations on our side. Were you able to get this resolved? If not, you can give support a call where we can look at the specific backend side of the return to see the specific reject from the state. Sometimes we get more detail than it reports to you.