Announcement

Collapse
No announcement yet.

Imperfect Return

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Imperfect Return

    I have a client whothe IRS rejected because dependent info did not match. We claimed their child last year and the IRS accepted the return. Why this year would the IRS say the info does not match? The childs name has not changed.

    Has anyone ever filed an imperfect return? What were the results? Also Drake says the state return can not be piggybacked. However we are not getting a Drake error message that the state is not going piggyback.

    #2
    What is the Question

    ...not trying to act smart-alek, but not sure I understand the question.

    What is being rejected? Your client? Your client's dependent? Your client's return?

    What constitutes an "imperfect" return? A return with a single mistake? A return that won't e-file? A return that Drake can't piggy-back? Is a return with a non-matching dependent an "imperfect" return?

    I did gather that you are being informed that a dependent doesn't "match." I you speaking of a descrepancy between the social security # and the name of the dependent? Is the dependent suddenly have a change in status, like suddenly being too old for CTC or EIC, or maybe eloping and getting married and not telling anyone? (This sounds far-fetched, but could produce exactly the results that you say you are getting)

    Comment


      #3
      If the IRS says they have something different, have the client contact SSA for a transscript for the child's SSN. Maybe there was an erroneous change made by SSA.

      Comment


        #4
        When someone else claimed the child

        I have seen this error when 2 individual are divorced and they both claim the child. The first one to files locks the second one. The second to file has to paper file.

        Dusty

        Comment


          #5
          Originally posted by tpnl View Post
          I have a client whothe IRS rejected because dependent info did not match. We claimed their child last year and the IRS accepted the return. Why this year would the IRS say the info does not match? The childs name has not changed.

          Has anyone ever filed an imperfect return? What were the results? Also Drake says the state return can not be piggybacked. However we are not getting a Drake error message that the state is not going piggyback.
          Can you post the Reject Code the IRS form, form sequence and field id? There are many codes for this wording. Having the detailed error information like the error code, form and field id will help locate the exact error.

          Here is the link to the forms and fields on each form:


          Here is a list of the error reject codes:


          0501 Qualifying SSN (SEQ 0015, 0085, 0155) of Schedule EIC and the corresponding Qualifying Child Name Control (SEQ 0007, 0077, 0147) must match data from the IRS Master File.

          0504 Dependent’s SSN (SEQ 0175, 0185, 0195, 0205) of Form 1040/1040A and corresponding Dependent Name Control (SEQ 0172, 0182, 0192, 0202) must match data from the IRS Master File.

          0506 Qualifying SSN (SEQ 0015, 0085, 0155) of Schedule EIC was previously used for the same purpose.

          0507 Dependent’s SSN (SEQ 0175, 0185, 0195, 0205) of Form 1040/1040A
          was previously used for the same purpose.



          0507 Dependent’s SSN (SEQ 0175, 0185, 0195, 0205) of Form 1040/1040A
          was previously used for the same purpose.

          Comment


            #6
            I believe tpnl is referring to the MeF "imperfect return" option. Kind of a cool option, but note IRS docs say the return will take 4-6 weeks to process.

            I've had my software fail to proforma the most up to date information for a child. For example, one return I did I had an incorrect SSN on there and had to fix it to file. When I proforma'd the return to the next year, it proforma'd the old SSN not the new one.

            There's also the possibility that last years return was not efiled. In which case the name or SSN could have been wrong last year as well.

            And if you changed software companies, I would not put a lot of trust in any conversion process. I'd be double checking it.

            Comment


              #7
              You maybe right, but this might not be the best customer service solution.

              Here is the link to the IRS information for Error Reject Codes - Self-Assist Solutions , http://www.irs.gov/efile/article/0,,id=180182,00.html .

              So if you can clear up the problem in less then 2 weeks you can help your client get their refund faster.

              Also, if you let the IRS resolve this problem, you might not know the final adjustment and assume next year that there was no problem in the past years.
              Last edited by gkaiseril; 01-29-2010, 01:44 PM.

              Comment


                #8
                The most common reason in my experience is Dusty's response. Someone else took the child.
                I have dealt with this by filing a paper return with the child included...if your client is the one that qualifies to take the child.
                I ask the client who took the child, and if they know, I ask for as much identifying information they can provide on that person, how they know or why they think this person may be the culprit.
                Then I include a Statement of Explanation with the return including all the info on the suspected person and the reason my client.
                The IRS will send a letter to the person that claimed the child asking for verification of qualification.
                My client will get their full refund, including the child as a dependent and the IRS will go after the other TP.

                If this is an accual name/SSN/DOB mismatch. My question would be...was your client's return e-filed last year? If so, it should have rejected. If not, it is probable that the SSN, etc, was not verified by IRS on the paper filed return
                Believe nothing you have not personally researched and verified.

                Comment

                Working...
                X