I am having an extraordinary number of rejected tax returns this year due to reject code 902, which is "SSN of primary taxpayer already used on a previously accepted return." All six of the rejects I have had are previous clients whose SSN#s are correct on the return, so somebody got hold of their info and is filing fraudulent returns using their names and SSN#s. Needless to say, I am freaking out. I don't know where the security breech is and I'm not getting any help from the IRS on this. They say the average of returns being filed by hijacked SSN#s is about 1%, but I'm a small office in a small town and I've only filed 30 returns so far, so my average is 20%. It seems like this should be investigated in order to prevent further damage (although I realize that a lot of the damage is already done and I won't know about it till after I file my clients who haven't come in yet).
Is anybody else having trouble like this? It seems too high a ratio to be "just the way it is" which is what my software company and the IRS are telling me.
Is anybody else having trouble like this? It seems too high a ratio to be "just the way it is" which is what my software company and the IRS are telling me.
Comment