1099 or W-2? How MSPs Should Classify Contractors

Almost every MSP I have worked with has, at some point, paid a technician as a 1099 contractor when that person should have been a W-2 employee. It usually is not intentional. It happens because a moonlighting tech starts helping out on weekends, or a help desk contractor becomes a full-time fixture, and nobody ever revisits the classification once the relationship changes. By the time it gets flagged, often in a payroll or workers comp audit, it can be an expensive problem to unwind.

This is one of the highest-risk areas in MSP bookkeeping because the line between a legitimate contractor and a misclassified employee is not about the paperwork you signed. It is about how the working relationship actually functions day to day.

The Test the IRS Actually Uses

The IRS does not look at whether you call someone a contractor or whether you have a signed independent contractor agreement. It looks at the underlying relationship using three categories of evidence, often called the common law test.

• Behavioral control — Do you tell them how, when, and where to do the work, or just what the end result needs to be?
• Financial control — Do they have a real opportunity for profit or loss, invest in their own tools and equipment, and work for other clients?
• Type of relationship — Is the work ongoing and indefinite, or tied to a specific project with a defined end?

A field technician who works a set schedule, uses your PSA and RMM tools, wears your company branding, gets assigned tickets by your dispatcher, and only works for your MSP looks like an employee under every part of this test — regardless of what the 1099 says.

Common MSP Scenarios That Get This Wrong

• A technician who started as a genuine side project and became your only field resource in that territory
• Help desk staff working set shifts through your ticketing system, paid a flat rate per hour
• A subcontracted "vCIO" who only ever works with your clients, under your branding, on your schedule
• Bringing back a former W-2 employee as a 1099 to avoid restarting payroll taxes and benefits

What Misclassification Actually Costs You

If the IRS or your state labor agency reclassifies a contractor as an employee, you are on the hook retroactively, not just going forward. That typically includes:

• Back federal payroll taxes (Social Security and Medicare, both the employer and often the employee share)
• Federal unemployment tax (FUTA) and state unemployment tax you never paid
• Penalties for failure to withhold and failure to file correct information returns
• Interest accruing from the original due date, not the date of discovery
• Potential exposure for unpaid overtime if the worker was misclassified as exempt as well as misclassified as a contractor

None of this is capped at "this year." If the relationship has looked like employment for three years, the exposure covers three years, multiplied across however many workers were classified the same way.

If You Think You Already Have a Problem

Do not just quietly switch everyone to W-2 next month and hope nobody asks why. A sudden mass reclassification with no explanation is itself a red flag. If you suspect you have contractors who should be employees, there is a legitimate path to fix it with reduced penalties: the IRS Voluntary Classification Settlement Program (VCSP) allows eligible employers to reclassify workers going forward while paying a small fraction of the payroll tax that would otherwise be owed, with reduced penalties and no audit of prior years for that issue.

This is exactly the kind of situation where you want your bookkeeper and your CPA looking at the same picture before you file anything. Fixing it correctly protects you far more than fixing it quietly.

What to Review Right Now

1. List every 1099 worker currently on your books and how long each relationship has run
2. For each one, ask honestly: do they set their own schedule, use their own tools, and work for other clients?
3. Check whether any former W-2 employees were converted to 1099 status without a real change in the work
4. Confirm your contractor agreements actually match how the work happens, not just how it is described on paper

Building It Correctly Going Forward

Once your books are clean and your payroll is running through Gusto, keeping this straight is mostly a matter of reviewing new working relationships as they start, not after they have run for two years. Genuine subcontracted work — a specialist brought in for a single project, a firm you refer overflow work to, someone who bills you an invoice for defined deliverables — is a completely normal and legitimate part of running an MSP. The risk is specifically in treating an ongoing, controlled, schedule-based relationship as if it were the same thing.