A second employer withholding account was opened under the same EIN, and four quarters of zero-wage returns were filed before the small business owner saw the conflict.
The landscaping company employed seven people and had filed every withholding return on schedule. A notice from the state department of revenue described a reopening event the owner had never requested. An actor had completed a second registration through the department's online business portal using the company's EIN and legal name, then filed returns showing zero wages and zero withholding owed. The portal did not block a duplicate registration against an active EIN. Legitimate returns showing real payroll now sat next to fraudulent zero-liability filings for the same periods.
The department's resolution path required an in-person audit of actual payroll records across the full conflict window. Until that audit closed, the small business owner carried an open compliance problem on an account that funds employee tax deposits. A wrong step in the response sequence can convert a fraud event into a liability assessment against the real employer of record.
For a small business owner who runs payroll, the employer withholding account feels like a completed filing chore, not a surface that can be cloned. The same EIN that tells the state who the lawful employer is also works as a registration key on portals that accept public identifiers as enough to start a new account. Treating each registration event, each filing period, and each status change as something that must be watched is the only way to catch a second account before zero-wage returns rewrite the compliance picture the real business spent years building.
Most Small Business Owners don't take action until they're forced to. By then, the exposure has already done its job. The RuleDraft Small Business Isolation Manual gives you the tested sequence to get ahead of the problem, instead of reacting to it.