A ruling has determined that a chief financial officer who spent years working for GFI as a contractor was, in fact, an employee — despite the company classifying the executive as an independent contractor throughout the engagement.

The decision puts a senior finance leader, not a gig worker or entry-level staffer, at the center of a worker misclassification dispute. That detail alone should catch HR and legal teams' attention: if a C-suite contractor can be reclassified as an employee, no layer of the contractor workforce is immune from scrutiny.

Why does seniority not protect a contractor label?

The case turns on a principle HR teams encounter repeatedly in misclassification disputes: what parties call a working relationship matters far less than how the relationship actually functions. Courts and agencies typically apply tests that weigh factors such as control over the work, integration of the role into the business, exclusivity of the engagement and the worker's opportunity for independent profit or loss.

A CFO role sits unusually high on several of those factors. Finance chiefs typically:

• work exclusively for one organization;
• integrate deeply into strategic decision-making;
• report into the CEO or board rather than operating as an outside service provider;
• direct internal teams and processes.

Each of those characteristics points toward employment rather than independent contracting. The ruling in the GFI matter confirms that the contractor label, however long it persisted — in this case, for years — cannot survive a factual record that looks like employment.

What does the ruling change for employers?

Nothing in the decision rewrites classification law. What it does is sharpen the practical warning for people-process decisions that HR leaders already face.

First, seniority is not a shield. Many organizations assume misclassification risk concentrates in lower-wage, high-volume contractor populations — drivers, delivery workers, project freelancers. A CFO being ruled an employee demonstrates that risk climbs the org chart.

Second, duration cuts against the employer. Years of continuous service strengthen the employee-side argument on integration and permanency, two factors most classification tests weigh heavily. Long-tenured contractors are, statistically speaking, the exposure employers should audit first.

Third, the consequences of reclassification compound quickly at the executive level. When a contractor becomes an employee retroactively, employers can face:

• back payroll taxes and withholding obligations;
• unpaid benefits participation, including retirement plan claims;
• overtime or minimum wage exposure where exemptions were never analyzed because the person was never on payroll;
• penalties tied to statutory contributions in the relevant jurisdiction.

At CFO compensation levels, each of those categories carries a dollar value far above what a typical misclassification claim involves.

Which employer obligations does this touch?

Reclassification decisions ripple through nearly every people process. Once a worker is deemed an employee, employers must revisit:

• payroll setup, tax withholding and year-end reporting;
• eligibility under benefits plans, including health, retirement and equity arrangements;
• leave entitlements and statutory contributions;
• onboarding documentation, policies and handbook coverage;
• exemption analysis under wage-and-hour rules, which is a separate question from contractor status.

That last point deserves emphasis. An executive reclassified as an employee is usually exempt from overtime — but exemption depends on duties and salary tests, and an employer that never ran those tests because the person sat outside HR's systems entirely may discover compliance gaps well beyond the classification question itself.

What should HR teams do now?

The practical response is an audit of long-tenured contractors, prioritized by integration into core operations. HR leaders should ask: does this person work predominantly for us? Do they manage our staff? Have they been with us for years under successive engagements? A "yes" to any of those questions warrants a fresh classification review with legal counsel, regardless of how senior or well-paid the individual is.

Contract language helps only when the underlying working arrangement matches it. Where the day-to-day reality looks like employment — as it apparently did for GFI's finance chief over a multi-year engagement — courts will keep ruling on the facts, not the paperwork. Employers that treat executive contractors as outside the scope of misclassification risk should expect more rulings like this one to test that assumption.