1. LandOffer
  2. Blog
  3. All articles
  4. Unrecognized Wages on an IRS Notice: Separate Payroll Errors from Employment Identity Theft

Workplace Rights

Unrecognized Wages on an IRS Notice: Separate Payroll Errors from Employment Identity Theft

Identify the IRS notice and tax year, compare wage records, and organize a documented response without assuming identity theft. Includes fictional CP01E and CP2000 cases, a wage reconciliation and a contact log.

10 min readLandOffer team

When an IRS notice lists wages you do not recognize, identify the notice number, tax year, requested action and response date before deciding what the discrepancy means. Compare the employer and wage details with your own records. A payroll reporting error, an unfamiliar employer name and possible employment identity theft require different evidence; one mismatch does not establish its cause.

This LandOffer.ai guide explains current U.S. agency instructions using entirely fictional records. It does not review anyone’s tax account, determine tax liability or recommend a personal amendment decision. No notice, Social Security number, payroll account or agency submission was accessed. The goal is to organize a specific, supported question for the right agency while keeping unresolved facts visible.

A professional compares separate official envelopes with an original employment ledger in a records reading room.

Start with the notice, not an identity-theft conclusion

Keep the complete notice, including its response form, attachments and envelope. Record the number printed on it, the year under review and the date it asks you to respond. Label the tax year separately from the notice’s arrival date. A 2026 paycheck cannot explain a wage item attributed to 2024 without evidence connecting the two.

Verify the correspondence using the matching notice information on IRS.gov before supplying sensitive information. Navigate to the official site yourself. For a known employer, use a payroll contact from your established internal directory rather than a new address in an unsolicited message. Do not send a full notice, identification document or SSN to an unknown recruiter, search-result advertisement or public discussion forum.

The distinction between two common notice types matters:

  • CP01E: The IRS says someone may have used your SSN for employment. Its notice page describes an identity-theft indicator and monitoring, with no currently known tax-account impact. Review the recommended protective steps and continue timely filing. This is different from a proposed adjustment requiring agreement or disagreement.
  • CP2000 series: Third-party information differs from the return. The notice describes proposed changes, is not a bill and may require a response. Follow its instructions and date. For wages neither you nor your spouse (if filing jointly) earned, the employment-identity-theft guidance directs immediate contact using the notice’s telephone or fax route.

These are summaries of the CP01E instructions and CP2000 series instructions, not interchangeable response scripts. Another notice number needs its own instructions. In particular, an informational CP01E does not cancel an action required by a separate CP2000.

Worked triage: two letters, two separate tasks

The following people, employers, dates and figures are invented. Neither example reproduces an IRS notice or proves that a particular real notice would contain these fields.

Case A — Celia’s informational notice. Celia receives a CP01E on October 6, 2026. It concerns possible employment misuse; she has not received a proposed wage adjustment. Her 2025 records show one known employer, Marlow Systems. She records the CP01E’s protective recommendations, plans an SSA earnings review and keeps ordinary tax-filing obligations separate. She does not invent an extra employer or an amount absent from the notice. The CP01E FAQ says the detected W-2 use may have been intentional or accidental. Celia records that uncertainty rather than treating the warning as a finding of deliberate fraud.

Case B — Dorian’s wage discrepancy. Dorian receives a CP2000 on October 7, 2026, concerning tax year 2024. The fictional notice requests a response by November 9 and lists $18,400 attributed to Kestrel Staffing. Dorian recognizes two other employers from that year but not Kestrel. His initial classification is “income attribution disputed; cause unknown,” rather than “confirmed identity theft.”

Triage field Celia: CP01E Dorian: CP2000
What is known Informational employment-misuse warning Proposed changes involving a named $18,400 wage item
What is not established Whether her earnings record contains an incorrect amount Whether the item reflects payroll error, another reporting issue or misuse
Immediate route Review CP01E guidance and earnings records Follow CP2000 response instructions; contact IRS promptly about the disputed wages
Evidence task Compare the relevant earnings year with retained employment records Match the listed employer, year and wage category against records; prepare a specific disagreement explanation
Closure condition Record review and any required follow-up documented IRS response addresses the disputed item; other agency corrections tracked separately

The November 9 date belongs only to this fictional letter. It is not a standard response period. Dorian sets an October 20 preparation checkpoint so a missing payroll answer will be noticed before his stated deadline. That checkpoint is his planning choice, not an IRS extension. He can see whether the packet is ready while there is still time to address missing evidence; assembling documents does not itself satisfy the notice.

If an actual deadline is close, an unresolved employer inquiry should not become a reason to ignore the notice. The CP2000 page describes requesting more time; a request should not be recorded as granted until the IRS confirms it. A qualified tax professional can help with an unclear response or the interaction with other return issues.

Build an employer and year record before choosing a cause

Start with a short factual inventory. For each employer, retain the legal name printed on the wage statement, your recognized workplace name, employment period, tax year, relevant wage box and document version. Where an EIN helps match records, keep it in the secure case file rather than an unnecessary shared summary.

An unfamiliar legal name can have an innocent explanation. A recognized payroll department may confirm an employer-of-record relationship or name change. That confirmation should identify which statement and period it explains. “We use a payroll company” is too vague to resolve an unrelated wage item.

A known employer can also report incorrect information. The IRS’s incorrect W-2 guidance begins with contacting the employer or payer. Request an issuer explanation or corrected document where appropriate; do not edit an issued W-2 yourself. A payroll representative acknowledging a problem is not evidence that a correction has reached every agency.

Compare matching categories. Net bank deposits are not the same as reported wages. Federal income-tax wages and Social Security or Medicare wages can differ; the IRS explains that certain salary reductions receive different treatment. Use the named box and year rather than assuming every total must agree. This is a reconciliation safeguard, not a calculation of anyone’s taxable income.

An alarming notice can make a quick explanation appealing. Keep a separate “not recognized” category when the employer and work cannot be connected to you. You can describe the discrepancy accurately before knowing who caused it. Do not fabricate a short employment period to make the table balance. If filing jointly, the disputed-wage question also needs to account for the spouse’s actual work before describing an item as neither person’s income.

A records specialist checks an original ledger against a chronological file while leaving an unanswered envelope separate.

Completed record packet and contact log

Dorian’s invented packet illustrates how to carry a specific question across payroll and agency channels. For simplicity, each recognized statement has the same amount in Box 1 (federal wages), Box 3 (Social Security wages) and Box 5 (Medicare wages). The CP2000 comparison uses Box 1; the SSA comparison uses Box 3. Real statements may differ.

2024 record Recognized work and evidence Amount being compared Current disposition
Marlow Systems January–August; retained W-2 and final payroll summary $52,000 in the specified wage fields Matches his retained records; no correction requested
Alder Research September–December; W-2 issued under Alder Services LLC $26,000 in the specified wage fields Payroll confirms the legal-name relationship on October 9; explanation saved
Kestrel Staffing No work, wage statement or payment recognized by Dorian $18,400 wage item on the fictional CP2000 Disputed; no conclusion about the cause
SSA annual record Saved October 8; 2024 Social Security earnings shown $96,400 $18,400 above the $78,000 recognized comparison total; agency review needed

The arithmetic is $52,000 + $26,000 = $78,000; $96,400 − $78,000 = $18,400. Matching differences help state the question but do not prove Kestrel caused the SSA entry. An annual total alone does not supply an employer-by-employer finding. Dorian asks SSA to review the attribution rather than presenting an inference as an agency determination.

His secure packet contains: the complete CP2000 and response form; both recognized W-2s; the relevant payroll summaries; Alder’s legal-name confirmation; the dated SSA record; and a one-page index identifying the disputed item. Originals remain intact. The index omits full identifiers, while any actual agency submission must provide the identifying information its instructions require through an appropriate secure route.

Prepared explanation, not a submitted tax response: “The notice concerns tax year 2024. I recognize the Marlow and Alder wages identified in my attached record index. I do not recognize employment with Kestrel Staffing or the $18,400 wage item attributed to it. Please review that attribution. The attached documents show the employment I can substantiate; they do not establish why the additional item was reported.”

The actual response form still needs completion and signature as directed. This paragraph cannot replace a notice’s required fields or individualized professional advice. Documents should support the specific disagreement without disclosing unrelated family, banking or employment information.

Date in the fictional case Channel and question Result actually recorded within the example
October 8 Personal record review Notice and SSA record saved; cause remains unknown
October 9 Established Alder payroll channel Legal-name explanation received; no Kestrel explanation
October 12 IRS contact route verified against CP2000 guidance Call attempted; no substantive answer or extension obtained
October 13 Official SSA appointment route Appointment requested; earnings correction not yet accepted
October 20 Dorian’s preparation review Draft packet assembled; response still needs notice-specific review and submission

This is a completed contact log with pending outcomes, not a success story. The packet is prepared, not sent. No IRS decision, SSA correction or identity-theft finding has occurred. Dorian keeps a separate reminder to complete the response before the fictional November 9 deadline.

Use SSA correction and identity protection for their own jobs

The SSA earnings-correction FAQ, dated August 11, 2026, says online correction may be available, but not to everyone. When unavailable, its instructions describe an office visit, identity verification and supporting information; SSA may request Form SSA-7008 in some cases. Follow the current route for your circumstances instead of assuming a universal online button or form requirement.

An SSA review does not answer a separate IRS notice for you. Likewise, an IRS acknowledgment does not prove an earnings record has been corrected. Retain each agency’s reference, documents requested, next step and eventual result. Check an updated record before marking that part closed.

Form 14039 also needs current, situation-specific handling. The February 2026 form includes fraudulent employment use of an SSN or ITIN among its listed scenarios. Therefore, “employment misuse never uses this form” is inaccurate. “Every unfamiliar wage requires this affidavit” is also unsupported. For CP01E specifically, its current FAQ says Form 14039 is not needed because the IRS has already added an indicator. Other situations require their own current instructions; do not file a duplicate for an incident already reported on that form. A form’s available checkbox does not override notice-specific guidance.

The IRS’s identity-theft resources describe additional protective steps, including an IP PIN and FTC recovery guidance. Those measures serve different purposes from correcting a wage item. An IP PIN does not by itself remove disputed earnings. Keep sensitive records out of ordinary workplace chat, and use official routes for identity verification.

Before closing your file, distinguish a prepared packet, delivery confirmation, agency acknowledgment and substantive resolution. If one remains missing, record what you will check next. You can return to LandOffer.ai for related workplace guidance; this task remains with your records, the responsible agencies and any professional adviser you choose.

Sources and Further Reading