Provide Which Dependent Results in Error Code to User

Related products:ProConnect

3 replies
34 views

Provide which dependent is the problem without calling support.

I recently filed a tax return that was rejected with the Code: IND-517-02. Basically a dependent has a tax return already filed for the IRS, but they didn't indicate they were eligible to be claimed as a dependent.

Which dependent, you may ask? Well, here's the solution provided in the rejection text by ProConnect:

'''
If multiple dependents are present in this return, review the Description field. There will be a number in brackets, [?], that identifies which dependent is causing this reject. For example: "[2]" will identify the second dependent from the top.
'''

No matter where I looked, I could not find any number in brackets. Finally, I talked to support. They asked for the submission ID (confirmation ID) and were able to tell me immediately which dependent was the issue. So I asked how I was supposed to find that out, and he said that you must contact support to get that info.

That's dumb. You have the info. Allow the info to be available to the tax return preparer so they can solve the issue without contacting support.

Errors & Diagnostics

BobKamman

Level 15

I thought the IND-517 meant ineligible dependent and the -02 meant the second one listed. Is that how it turned out? So maybe they're not using brackets anymore.

PatrickSanfordAuthor

Level 3

That's what I initially thought too, but after talking with the client and ProConnect support, we found out it was the 3rd dependent who was the issue. Not the second one.

R

renateschucpa

Level 2

I have the same issue. I used Drake tax before ProConnect & it would give you a diagnostic report explaining exactly the issue - which dependent was the issue, the SSN & how to fix. I could print & save so share with the client. Now in ProConnect I have the same issue but there is no diagnostic to print out, just a vague “solution” that tells you to review the Desctription field. There is no description field & no efile diagnostic report (like there is in ProSeries or Drake). Nothing to print - I just have to tell the client and try to figure out which dependent is the issue. After contacting support, they were able to tell me from looking on the back end. Great - but it’s ridiculous that preparers would have to contact support each time for each reject! How is there an audit trail of what the preparer did and WHY? There is nothing to document or show the client why the return had to be refiled without a certain dependent - just going off what support tells you. Lacerte and ProSeries provides this. It needs to be developed & available in ProConnect also.

Sign up

Login with SSO

Let's get you signed in

Login with SSO