Let’s talk about one of the sneakiest ways small businesses get themselves into hot water: calling someone a “contractor” when the IRS (or your state, or the Department of Labor) would call them an employee.
I get why it happens. Contractors are easier. No payroll taxes, no benefits, no overtime, no unemployment insurance, less paperwork. You hire someone, hand them a 1099 at the end of the year, and move on with your life. It’s efficient.
The problem is that “contractor” isn’t a label you get to choose just because it’s convenient. It’s a legal classification, and the government has a very specific definition of what makes someone a contractor versus an employee, and it boils down to how much control you have over how, when, and where they do the work. If you’re telling someone what hours to work, giving them a company email address, supervising their day-to-day work, and they’ve been doing this for you full-time for two years… that’s probably not a contractor. That’s an employee wearing a contractor’s name tag.
And here’s the part that catches people off guard: getting this wrong isn’t just a slap-on-the-wrist mistake. It’s expensive, and it can snowball really fast.
What the misclassification actually costs you
If the IRS or Department of Labor decides your contractor should’ve been an employee, you’re not just fixing the label going forward. You’re on the hook retroactively – which means:
Back taxes. You owe the employer’s share of Social Security and Medicare taxes you should’ve been paying all along, plus you’re liable for the income tax and employee-side FICA you didn’t withhold. Yes – you are responsible for the employee portion. There’s a slightly reduced-rate option under IRS rules (Section 3509) if you can show you genuinely thought the worker was a contractor and filed their 1099s properly – but that break disappears if the IRS decides you knew better and just didn’t bother. In that case, you’re looking at the full amount, no discount.
Overtime and back wages. This is the one everyone forgets. If that “contractor” was actually a non-exempt employee, they were entitled to overtime pay any week they worked more than 40 hours. Contractors don’t get overtime, but employees do. So now you owe back overtime for however long the misclassification lasted, and if it’s found to be a willful violation under the Fair Labor Standards Act, you can owe double that amount in liquidated damages. Many businesses have paid out hundreds of thousands of dollars in back wages because of this.
Penalties on top of penalties. Because you classified this employee as a contractor – you didn’t file a W-2 for them. That’s a per-form penalty. Fail to withhold taxes you should’ve withheld? That’s roughly 1.5% of wages plus 40% of the unwithheld FICA, plus a failure-to-pay penalty that keeps accruing monthly. And if the IRS decides it wasn’t an honest mistake (meaning it looks intentional) the penalties jump dramatically. And to top it off, there’s technically criminal exposure on the table too. Something nobody wants.
Add it all up – back taxes, back overtime, interest, penalties, maybe legal fees – and a “cost-saving”, convenient contractor arrangement can turn into one of the most expensive decisions a small business ever made.
And here’s the worst part: it doesn’t stay isolated
Here’s what a lot of business owners don’t realize until it’s too late. Misclassification cases rarely start as “let’s audit your entire workforce.” They start small – usually a single worker files for unemployment after you cut them loose, or someone complains to the Department of Labor, or the IRS flags something on a return. That’s the trigger.
But once an auditor is in the door, they don’t just look at that one person. They look at how you classify everyone doing similar work. And here’s the kicker: if one contractor gets reclassified as an employee, every other worker doing the same job, under the same conditions, tends to get swept in right along with them – even the ones you were genuinely careful about, even the ones who seem like textbook contractors on paper. The logic is simple from the auditor’s side: if this person’s job looks like an employee’s job, so does everyone else’s doing the same thing.
So, a single disgruntled ex-contractor, or one routine audit, can turn your entire contractor list into a payroll problem overnight – with back taxes, back overtime, and penalties applying across the board, not just to the one person who triggered it.
The takeaway
This isn’t about scaring you out of ever using contractors – plenty of contractor relationships are completely legitimate, and they’re a great tool when they’re set up right. The point is that classification isn’t a paperwork formality you can wing. It’s worth actually reviewing how you’re using contractors: who’s setting the hours, who owns the tools, how much oversight there is, whether this looks and feels like a job or a project.
If you’re not sure where your contractors land, that’s exactly the kind of thing worth getting a second set of eyes on before the government does it for you. Happy to help you take a look.
Enjoyed this article? Consider Sharing
Author
