CP2000 Based on a Wrong W-2 or 1099: How to Fight Bad Third-Party Data

Sometimes the CP2000 is right and you forgot a 1099. Sometimes the CP2000 is wrong because the 1099 is wrong. Those are completely different problems, and the second one is more common than people think.

The IRS matches what payers report. It does not independently verify that the payer got it right. If a brokerage, an employer, a payment platform or a client filed a bad form, the CP2000 will faithfully repeat the error, add tax to it and charge interest. Your job is to break the chain at the source.

The common errors

Here is what I see most often when a CP2000 rests on bad information:

• Wrong amount. A typo, a gross figure reported where a net figure belonged, or a payment that was later reversed.
• Wrong year. A December payment reported in the wrong tax year.
• Wrong person. Income reported under your SSN that belongs to someone else, including joint accounts where you own only part of the income.
• Duplicate reporting. The same dollars reported twice by two different payers or on two different form types.
• Income that is not income. Amounts reported that are nontaxable, such as a rollover or a return of your own money.
• Identity theft. Wages or payments from a payer you have never heard of.

Each one has its own fix. But all of them start in the same place.

Start with the payer

The IRS points taxpayers to the payer first. Its guidance on incorrect W-2 and 1099-R forms (Tax Topic 154) says that if the information on the form is incorrect, contact your employer or payer. The AUR manual says the same thing from the IRS side: if a taxpayer disclaims knowledge of the income or disputes the amount, the employee is told to "inform the taxpayer to contact the payers in dispute."

The IRM even contains model language for a letter to a taxpayer whose dividend dispute lacked documentation: "Please contact the payer for written verification that the information furnished to us is incorrect. We are unable to change our proposal without this information." That sentence tells you exactly what wins these cases. Written verification from the payer.

What to ask the payer for, in order of strength:

1. A corrected information return, filed with the IRS and furnished to you.
2. A signed letter on the payer's letterhead stating the correct amount, year or payee and explaining the error.
3. Account statements or ledgers showing the true amounts, if the payer will not do either of the above.

Responding to the CP2000 while you wait

Payers move slowly. The response date on your CP2000 does not. Do not let the deadline pass while you wait for a corrected form.

Respond by the date on the notice. Mark the disputed item as disagreed, explain the error in two or three sentences, and attach whatever you already have: your own records, correspondence showing you asked the payer for a correction, and the payer's response if you have it. If you need more time, the IRS says you can request it by sending an extension request with your reply. Then send the corrected form or payer letter as soon as it arrives. For the overall response process, see how to respond to a CP2000.

When the payer will not cooperate: Form 2624

Some payers have gone out of business. Some ignore you. Some insist they are right when they are not. The AUR program has a tool for this.

Under IRM 4.19.3.23.9.6, AUR will contact a payer only when you return a completed Form 2624, Consent for Third-Party Contact, for the disputed payer. You need a separate Form 2624 for each payer. The IRS then sends Letter 2625-C to the payer to verify the information, following the third-party contact rules.

That is a meaningful step. You are asking the IRS to go to the source. If the payer cannot back up what it reported, that helps you. Third-party contacts in general are covered in third-party contacts during an audit.

Errors the IRS already knows about

You are not always the first to notice. The AUR program maintains a Payer Agent file, which IRM 4.19.3.6 describes as a compilation of information return documents "verified as erroneously filed or processed or determined potentially fraudulent." If a payer has told the IRS that it filed bad forms for a tax year, AUR examiners see an indicator on the case.

The IRM also tells AUR examiners who receive information from a payer or taxpayer that a proposed underreporting resulted from a payer reporting error or payroll mistake to forward it to the site Payer Agent Coordinator. If the error affected many people, say so in your response. It helps the IRS see the pattern.

Income that belongs to someone else

Joint accounts produce a lot of CP2000s. IRM 4.19.3.5.3 recognizes joint ownership when two or more names are on the form, and it provides procedures when the taxpayer reports the appropriate percentage. If you reported your share and the IRS proposes tax on the full amount, show the ownership and show where you reported your portion.

If the income is not yours at all and you do not recognize the payer, think identity theft. The IRS CP2000 page says that if someone used your identity, report it using Form 14039, the Identity Theft Affidavit. Do that alongside your CP2000 response, not instead of it.

The statutory backstop: IRC 6201(d)

Here is the part most people miss. Congress addressed bad information returns directly. IRC 6201(d) provides that in any court proceeding, if a taxpayer asserts a reasonable dispute about an item of income reported on an information return filed by a third party, and the taxpayer has fully cooperated with the IRS, the IRS has the burden of producing reasonable and probative information concerning the deficiency in addition to the information return.

Read the conditions carefully, because they are real:

• It applies in a court proceeding. It is not a rule the AUR examiner applies to your CP2000 response.
• The dispute must be reasonable. A bare denial is not enough.
• You must have fully cooperated. The statute describes cooperation as providing, within a reasonable period, access to and inspection of all witnesses, information and documents within your control, as reasonably requested.

So 6201(d) rewards exactly the behavior that also wins at the administrative level: respond, document, cooperate. If you ignore the CP2000 and later argue the 1099 was wrong, you have made the statute harder to use. More on proof burdens in burden of proof in an audit.

If the form is right but your return was wrong

Sometimes the investigation reveals the payer was right. Then the honest answer is to agree to the correct amount. If you also have related deductions or basis that were not on the return, include them. The IRS says to file Form 1040-X with the CP2000 response only if the changes are correct and you have other income, credits or expenses to report, writing "CP2000" across the top.

And if the same error happened in other years, fix those too. The IRS CP2000 page notes you may need to amend prior years with the same issue. Better that than a second notice next year.

After the case closes

If the CP2000 became an assessment before you could get the payer's correction, you are not out of options. AUR handles late responses and post-assessment requests as reconsideration cases under IRM 4.19.3.27. The corrected form you finally got from the payer is exactly the kind of new information reconsideration exists for. See what to do after an ignored or missed CP2000.

Bad data in, bad notice out. Fix the data, and the notice fixes itself.