Contractor vs. Employee: The Test the IRS Uses (And How Companies Fail It)

A company we knew paid a worker as a contractor for two years. The worker signed a contractor agreement. The agreement said "independent contractor" in the heading. The company issued 1099s at year end and the worker handled their own taxes.

At the two-year mark, the worker filed for unemployment benefits after the engagement ended. The state investigated. The state determined the worker was an employee. The company owed two years of back payroll taxes, employer contributions, and penalties. The contractor agreement was irrelevant to the determination.

This is not an unusual outcome. The misclassification is common. The exposure is real.

Why the agreement does not determine the classification

The IRS and most state labor agencies determine worker classification based on the actual nature of the relationship, not on what the parties agreed to call it. A contract that says "this is a contractor relationship" does not make it one. What makes it one is the facts.

The primary standard the IRS applies is the right-to-control test, evaluated across three categories: behavioral control, financial control, and the type of relationship.

Behavioral control covers whether the company has the right to direct and control what the worker does and how they do it. A worker who is told when to work, where to work, what tools to use, and how to perform each task is exhibiting the indicators of employment. A worker who is given a result to achieve and determines their own method, schedule, and tools is exhibiting the indicators of contracting.

Financial control covers whether the company controls the economic aspects of the worker's relationship with the business. An employee is paid a regular wage regardless of profit or loss. A contractor is paid for a deliverable, can realize profit or loss on the engagement, invests in their own equipment, and typically works for multiple clients. A worker who depends entirely on one company for income, is paid hourly, and uses the company's equipment and facilities is financially more like an employee than a contractor, regardless of the contract.

The type of relationship covers whether there is a written contract, whether the company provides employee benefits, whether the relationship is permanent or project-specific, and whether the work performed is a key aspect of the company's regular business. A software company that pays a worker to develop software full-time, indefinitely, is in a different position than a law firm that hires a caterer for a single event.

The specific behaviors that create exposure

The misclassification scenarios we have seen most often share recognizable patterns.

The full-time exclusive contractor. A worker engaged 40 hours per week, working only for one company, on that company's systems, following that company's processes, classified as a contractor because they are paid a fixed monthly fee instead of a salary. This classification does not survive scrutiny. The exclusivity and integration into the company's operations point strongly toward employment.

The permanent temporary contractor. A worker who has been classified as a contractor for multiple years, doing work that is central to the company's operations, on a relationship that has no defined project end date. "Permanent" and "contractor" are difficult to maintain simultaneously.

The controlled contractor. A worker who is given specific hours, specific methods, specific tools, and reviewed on the company's performance management cycle. The degree of behavioral control is the employment indicator the IRS weights most heavily.

What misclassification actually costs

Back payroll taxes are the primary exposure. The employer owes the employer's share of Social Security and Medicare taxes for the misclassified period, plus any state unemployment taxes that should have been paid. The IRS also assesses interest and penalties on the unpaid amounts, and the penalty structure accelerates for intentional misclassification.

State exposure varies but is often larger than federal exposure. States have their own tests, which in some cases are stricter than the federal standard. California's ABC test, for instance, starts with a presumption of employment and requires the company to prove all three components of the test to establish contractor status.

The worker's exposure is also real. A worker who was paid as a contractor and paid self-employment tax on those earnings can recover the overpaid portion if the relationship is reclassified. This is not a clean outcome for the company.

Before you sign the next contractor agreement

The question to answer honestly before classifying a worker as a contractor: if you described the actual working relationship to an IRS auditor, would they agree with the classification? Not whether the agreement says contractor, not whether the worker wants to be a contractor, but whether the facts of the relationship support it.

If they would not, the agreement is not protection. It is documentation of a misclassification. The contractor agreement does not set the classification. The actual relationship does. Most companies issuing 1099s do not know this clearly enough. We are telling you before you find out the way the company in that story did.