Employee vs. Independent Contractor: How the IRS Decides Worker Classification

If your business has grown to the point where you need help and you’re trying to figure out whether that help should come on as a 1099 contractor or a W-2 employee, you’ve landed in one of the more consequential decisions a growing business makes. It feels like a paperwork question. It’s actually a legal classification that the IRS, the Department of Labor, and often your state all have an opinion about, and that opinion doesn’t bend just because it would be more convenient for your cash flow or your payroll setup.

Here’s why this matters more than it might seem to at first glance. The label you put on the relationship, “contractor” or “employee,” doesn’t actually determine the classification. The IRS looks at how the relationship actually functions, not what you called it in an email or a contract.

Let’s walk through how the IRS actually decides this question, what happens when a business gets it wrong, and how to make and document a defensible decision the first time.

Why the Classification Question Comes Up Now

Most businesses don’t sit down and deliberately study worker classification rules before they need help. They need someone to build a website, cover overflow bookkeeping work, or handle deliveries, and the fastest path feels like just handing them 1099 paperwork and moving on. No payroll setup, no withholding, no employer’s share of payroll taxes. It’s simpler in the short term.

That simplicity is exactly why misclassification is such a common trap. The 1099 route looks administratively lighter for the business, and it’s true that some workers genuinely prefer the flexibility of contractor status. But plenty of workers who agree to 1099 treatment are looking at a paycheck with nothing withheld and assuming that means more money in their pocket, not realizing they’ve just become a small business owner with a very different tax bill waiting for them.

None of that changes how the IRS evaluates the classification question - the test doesn’t care what either side prefers or expects, but it does mean a worker’s enthusiasm for contractor status isn’t always the informed, mutual agreement it looks like on the surface. The problem shows up later, usually when the IRS, a state unemployment agency, or a worker filing for unemployment benefits after the relationship ends raises the question of whether the classification was ever correct.

The IRS Common Law Test: Three Categories, Not Twenty Factors

For years, the IRS evaluated worker classification using a sprawling 20-factor test that was unwieldy even for tax professionals to apply consistently. The IRS has since consolidated those factors into three broader categories, generally referred to as the common law test. No single factor is decisive on its own. The IRS looks at the entire relationship and weighs the evidence in each category.

Behavioral Control

This category asks whether the business controls, or has the right to control, what the worker does and how the worker does it. The key phrase there is “right to control.” Even if you never actually exercise that control day to day, having the contractual or practical authority to do so weighs toward employee status.

Specific things the IRS looks at include:

Instructions about when, where, and how to work. A worker who’s told to be at a specific location during specific hours, using specific tools or software, and following a specific process looks more like an employee than a contractor. A genuine contractor is typically told what result is needed, not exactly how to produce it.

Training. If you’re training someone on your specific procedures, methods, and internal systems, that’s evidence of behavioral control. Independent contractors generally already have the expertise and don’t need to be trained on how to do the work itself.

Evaluation systems. Employees are commonly evaluated on how they perform the work itself, the process. Contractors are more commonly evaluated only on the end result.

Financial Control

This category looks at whether the business controls the economic aspects of the worker’s job. Several sub-factors matter here.

Significant investment. Does the worker have a meaningful financial investment in the equipment, tools, or facilities used to do the work? A contractor who owns their own equipment, software licenses, and workspace looks different from someone using only what the business provides.

Unreimbursed expenses. Contractors more commonly bear their own business expenses without reimbursement. An employee typically gets expenses reimbursed or has them covered directly by the employer.

Opportunity for profit or loss. This is one of the more telling indicators. A genuine contractor can make more money by working efficiently, negotiating better rates, or managing costs well, and can also lose money on a job that goes poorly. An employee who’s paid a set hourly or salary rate regardless of how the underlying project performs financially doesn’t have that same risk and reward exposure.

Availability to the market. Does the worker actively market their services to other businesses and clients, or does this one business represent effectively their entire income? A worker who maintains their own business name, website, and client roster looks more like a contractor. A worker who works exclusively for one business, indefinitely, looks more like an employee, even if they’re nominally free to take other clients.

Method of payment. Contractors are typically paid a flat fee per project or per job. Employees are typically paid by the hour, week, or salary on a regular, guaranteed schedule regardless of output.

Relationship of the Parties

This category examines how the business and the worker themselves understand and structure the relationship.

Written contracts. A written independent contractor agreement is evidence of intent, though it’s not determinative on its own. The IRS and courts will look past the label in the contract if the actual working relationship contradicts it.

Employee-type benefits. Providing insurance, a retirement plan, paid vacation, or sick pay is strong evidence of employee status. Genuine contractors don’t typically receive these benefits because they’re not employees of the business paying them.

Permanency of the relationship. An indefinite, ongoing relationship with no defined end point looks more like employment. A relationship tied to a specific project or a defined term, after which the arrangement naturally concludes, looks more like a contractor engagement.

Key activity of the business. If the services the worker provides are a key part of the business’s regular activity, that leans toward employee status. Let’s say you run a landscaping company and the person mowing lawns five days a week is providing the core service your business sells. That looks very different from a landscaping company hiring an outside CPA a few hours a year to prepare its tax return. The CPA is providing a service that supports the business but isn’t the business’s core activity, which is a hallmark of a genuine contractor relationship.

A Tale of Two Hires

Let’s make this concrete with two hypothetical scenarios.

Let’s say you run a small marketing agency and you bring on Priya to design a new logo and brand package for a client. Priya runs her own design studio, has her own clients beyond you, uses her own design software and equipment, quotes a flat project fee, sets her own hours, and delivers the finished files when the project is done. There’s no ongoing relationship beyond this project, no benefits, and she has real opportunity for profit or loss depending on how efficiently she works. That’s a defensible contractor relationship across all three categories.

Now let’s say you run the same agency and bring on Marcus to handle client account management. Marcus works from your office during your standard business hours, uses your project management software exclusively, reports to your account director, has no other clients, is paid a fixed amount every two weeks regardless of how many accounts he manages, and has been in this arrangement for two years with no end date in sight. Even if you call Marcus a contractor and he signs a contractor agreement, this relationship looks like employment under the common law test. The label doesn’t change the substance.

That second scenario is where misclassification typically happens, not through bad intent, but through a business retaining someone in a way that functionally became an employment relationship over time without anyone revisiting the classification.

What Getting It Wrong Actually Costs

If the IRS or a state agency determines that a worker you classified as a contractor should have been an employee, the consequences aren’t limited to a polite correction going forward. The business becomes liable for the employment taxes it should have withheld and paid all along.

That includes the employer’s share of Social Security and Medicare taxes (FICA) that should have been matched, the employee’s share of FICA that should have been withheld, federal unemployment tax (FUTA) that should have been paid, and in many cases the income tax that should have been withheld from wages. On top of the tax itself, the IRS assesses penalties for failure to withhold and failure to deposit, plus interest accruing from the original due dates, which can span years if the misclassification went undetected for a while.

Depending on the facts, particularly whether the misclassification was found to be intentional, penalty rates vary. Even in cases treated as an honest, good-faith mistake, the combination of back taxes, penalties, and accumulated interest across multiple years and potentially multiple misclassified workers can represent a serious financial hit to a small business, on top of the disruption of unwinding the arrangement and potentially owing benefits retroactively as well.

Form SS-8: Asking the IRS for an Official Answer

Either the worker or the business can file Form SS-8, Determination of Worker Status for Purposes of Federal Employment Taxes and Income Tax Withholding, to formally ask the IRS to weigh in on a specific working relationship. The IRS reviews the facts submitted and issues a determination.

In practice, workers file this form more often than businesses do, frequently after a relationship has ended and the worker is trying to establish employee status retroactively, for reasons ranging from unemployment claims to disputes over unreimbursed business expenses.

Businesses are often reluctant to file Form SS-8 voluntarily, and it’s easy to see why. The process invites direct IRS scrutiny of a relationship the business may have already structured a certain way for cost or administrative reasons, and an unfavorable determination creates a paper trail that makes it harder to argue for relief later. Filing isn’t required, and most businesses instead work with a tax professional to evaluate the relationship privately against the common law factors before deciding how to proceed.

Section 530 Safe Harbor: Relief for Reasonable, Consistent Treatment

Congress created a provision, generally referred to as Section 530 relief after its place in the Revenue Act of 1978, that can protect a business from retroactive reclassification liability even if a worker technically should have been treated as an employee under the common law test.

To qualify for Section 530 relief, a business generally needs to show three things. First, a reasonable basis for treating the worker as a contractor, which can come from reliance on a prior IRS audit that didn’t challenge the classification, a long-standing industry practice of treating similar workers as contractors, judicial precedent, or advice from a professional. Second, consistent treatment, meaning the business treated this worker and all similarly situated workers the same way, as contractors, without flip-flopping. Third, that the business filed all required 1099 forms consistent with contractor treatment for the relevant years.

If a business meets these requirements, Section 530 can prevent the IRS from retroactively reclassifying the worker and assessing back employment taxes for prior periods, even though it doesn’t change how the worker should be classified going forward. It’s a shield for the past, not a determination about the future.

This relief is worth understanding before you assume a misclassification issue is a lost cause. It’s also a strong argument for consistency: treating one contractor differently from another performing substantially similar work under similar conditions is exactly the kind of inconsistency that can defeat a Section 530 defense.

The Voluntary Classification Settlement Program

If you’ve concluded, on review, that workers you’ve been treating as contractors should really be classified as employees going forward, the IRS offers a path to fix that without full retroactive exposure. It’s called the Voluntary Classification Settlement Program, or VCSP.

Through the VCSP, an eligible business can voluntarily reclassify a class of workers as employees for future tax periods in exchange for limited liability for the past. Under the program, the business pays a reduced amount, generally around 10 percent of the employment tax liability that would have been due on compensation paid to the reclassified workers for the most recent tax year, calculated under a reduced rate structure. In exchange, the business isn’t liable for the rest of the back employment taxes, penalties, or interest on those workers for prior years, and isn’t subject to an employment tax audit for those workers for prior years.

To participate, a business generally needs to have consistently treated the workers as contractors, have filed all required 1099 forms for the last three years, and not currently be under an employment tax audit by the IRS or a worker classification audit by the Department of Labor or a state agency. The application is made using Form 8952.

The VCSP is worth serious consideration for a business that recognizes it has workers who no longer fit the contractor mold, whether because the relationship evolved over time or because the original classification decision doesn’t hold up on closer review. It converts an open-ended, unpredictable liability into a known, bounded cost, and gets the business into a compliant posture going forward.

Some States Apply a Stricter Test Than the IRS

Everything above describes the federal common law test. It’s worth knowing that a number of states apply their own worker classification tests for state law purposes, such as unemployment insurance, workers’ compensation, and wage and hour law, and some of those tests are meaningfully stricter than the federal standard.

California and Massachusetts, among others, apply versions of what’s commonly called the ABC test. Under an ABC test, a worker is presumed to be an employee unless the business can affirmatively prove all three of the following: the worker is free from the business’s control and direction in performing the work, the worker performs work that’s outside the usual course of the business’s activities, and the worker is customarily engaged in an independently established trade, occupation, or business of the same nature as the work performed.

That third prong in particular is stricter than anything in the federal test, and the second prong, work outside the business’s usual activities, can disqualify workers who’d pass the federal test without much trouble. A business operating in or hiring workers located in an ABC test state needs to evaluate classification against both the federal common law test and the relevant state test, because passing one doesn’t guarantee passing the other.

When a Contractor Relationship Genuinely Makes Sense

None of this is meant to suggest contractor relationships are inherently risky or that businesses should default to employee classification out of caution. Plenty of contractor relationships are entirely legitimate and serve both the business and the worker well. The relationship tends to hold up when the worker runs their own independent business, serves multiple clients, sets their own methods and schedule, provides their own tools and equipment, and is engaged for a defined project or scope rather than an open-ended role performing the core function of your business indefinitely.

A few practical steps make a real difference in supporting a contractor classification, whether or not it’s ever questioned.

Use a written independent contractor agreement. Spell out the scope of the project, the deliverables, the payment structure (project-based or milestone-based rather than hourly wage-like payments), and language confirming the worker’s independence, including their right to work for others and their responsibility for their own tools, expenses, and taxes.

Document the business reasons for the classification. Keep a brief record of why the relationship was structured as a contractor engagement, referencing the specific facts, the worker’s own business, the defined scope, the lack of control over methods, and so on. If the relationship is ever questioned, having contemporaneous documentation of your reasoning is far more persuasive than reconstructing the justification after the fact.

Revisit the classification periodically, especially for long-running relationships. A contractor relationship that starts out clearly independent can drift toward employment over time, more hours, more integration into daily operations, more direction over how the work gets done. If a contractor relationship has been running for a year or more, it’s worth checking whether the facts on the ground still match the original classification.

Treat similarly situated workers consistently. As discussed above with Section 530 relief, inconsistent treatment of workers doing substantially similar work under similar conditions undermines your position no matter how well-documented any individual relationship is.

What to Do If You’re Not Sure

If you’re looking at a working relationship and genuinely can’t tell which way the common law factors point, that uncertainty itself is useful information. Close calls are exactly the situations where getting a second opinion before you finalize the classification, rather than after a dispute arises, saves real money and stress.

For anyone reading this who received a 1099 form and is trying to sort out what it means for their own return rather than deciding how to classify someone else, I covered that side of the picture in 1099-NEC vs. 1099-MISC: Understanding Contractor Tax Forms.

What Comes Next

Working through the classification question is really the first decision point. Once you’ve made the call that a worker is genuinely an employee rather than a contractor, a whole separate set of obligations kicks in: payroll setup, tax withholding, employer tax deposits, workers’ compensation coverage, and new-hire reporting requirements, among others. I’ll cover exactly what that involves in a follow-up post on hiring your first employee, so if you’ve landed on “employee” after working through this framework, keep an eye out for that.

The information in this post is educational in nature and hasn’t been tailored to your specific business or worker relationships. Worker classification determinations depend heavily on the specific facts of each situation, and state law can add requirements beyond the federal test discussed here. For personalized guidance on classifying a specific worker, evaluating past classification decisions, or considering the Voluntary Classification Settlement Program for your 2026 filings, please schedule a consultation.