Can Someone File a Tax Return Using My Stolen Personal Information?
An e-filed return bounces back as a duplicate, or a notice arrives about income from a job that never existed, and the sinking realization sets in: someone else may have already filed a tax return using a stolen identity. It happens more often than most people expect, and there are established steps for sorting it out.
In short
Yes, tax-related identity theft is a recognized and fairly common form of fraud, where someone uses another person’s name and Social Security number to file a return and claim a refund before the real taxpayer does. It’s typically discovered when a legitimate e-filed return gets rejected as a duplicate, or when a notice arrives referencing income or a return the actual taxpayer didn’t file. The specific resolution process can vary depending on how the fraud was discovered and what stage the return is at.
How this kind of fraud typically happens
Tax identity theft relies on having enough personal information — usually a name, date of birth, and Social Security number — to file a plausible-looking return. That information can come from a wide range of sources, including data breaches, phishing attempts, or stolen mail, and often has nothing to do with any mistake by the taxpayer themselves.
- It’s usually discovered at filing time. The most common first sign is an e-file rejection notice saying a return with that Social Security number has already been filed for the year.
- Sometimes a notice arrives instead. A letter referencing wages from an unfamiliar employer, or a request to verify identity before a return can be processed, can also be the first indication something is wrong.
- The fraudulent return is usually filed early. Fraudulent filers often submit before the real taxpayer does, aiming to claim a refund before the legitimate return is on file.
What generally happens next
Once tax identity theft is suspected, there’s a general process, though the exact steps and timeline depend on the specifics of the case. Typically, the taxpayer files their legitimate return on paper along with an identity theft affidavit, which flags the account for review. Tax authorities then investigate which return is legitimate, a process that can take a significant number of months. In many cases, taxpayers are issued a special identity protection number to include on future returns, which helps prevent a repeat of the same problem. Anyone in this situation should treat their specific notice or rejection message as the most reliable guide, since details can differ from one case to the next.
Why the wait can be so frustrating
Because a suspected fraudulent return has to be investigated before the legitimate one is processed, refunds in these cases are often delayed well beyond the usual timeline, which overlaps with — but is a distinct problem from — ordinary reasons a refund gets delayed or general reasons a refund is slow to arrive. It’s reasonable to expect the resolution to take longer than a typical return, and checking status updates through official channels rather than assuming a specific timeline can reduce some of the frustration.
Protecting records and reducing future risk
Because tax identity theft depends on stolen information rather than any error in past filings, reviewing how long old tax documents and notices are kept is still useful context — see general guidance on how long to keep tax records for how documentation factors into resolving a disputed return. It’s also worth understanding what happens if a return is filed late, since a fraud-related delay in getting a legitimate return processed is treated differently than a taxpayer simply filing behind schedule.
Putting it in perspective
Tax-related identity theft is a real and recognized problem, not a sign that anything was done wrong by the taxpayer, and it has an established, if sometimes slow, resolution path. The details of any individual case — how the fraud was discovered, what documentation exists, and what notices have already been received — shape how it unfolds, so reading each notice carefully is more useful than assuming the general process applies exactly the same way every time.