New Zealand | Contractor misclassification | Converted to compliant employee in one week
Based on real client situations, amalgamated for anonymity.
Key takeaways
- A contractor who is integrated into daily operations, uses company systems, and reports to a manager can already be an employee in substance, regardless of what the contract says.
- Converting the paperwork is the easy part. The harder question is what liability accrued during the period the relationship was misclassified, and that needs its own assessment.
- Once employment terms were agreed and verified, the conversion itself took about a week, proof that getting compliance right and moving quickly are not competing goals.
- The fix gave the individual real protections a contractor agreement never provided: leave, benefits, and statutory entitlements.
- This is not a New Zealand-specific risk. Any jurisdiction with a contractor-versus-employee test carries the same exposure.
Teamed is the trusted global employment expert for companies who need the right structure for where they are, and trusted advice for where they're going, from first hire to their own presence in-country.
This case looks at a mid-market education technology company that had, without quite realising it, been running an employment relationship through a contractor agreement. The fix was not complicated once the business asked the right question. Once the terms were agreed, converting the relationship into compliant employment took about a week. The right structure for where you are, trusted advice for where you're going, is the difference between a contractor arrangement that quietly turns into legal exposure and one that gets caught and corrected before it costs anything.
The situation, anonymised
A mid-market education technology company had engaged an individual as an independent contractor to support a specific piece of work. Over time, the scope expanded organically, as it often does. The individual moved from delivering discrete pieces of work to functioning as a core member of the team: attending internal meetings, reporting to a manager, using company systems, and working exclusively for the client for well over a year. Nobody set out to misclassify anyone. The relationship simply evolved past the boundaries of a genuine contractor engagement, and the paperwork never caught up.
The question that revealed the trap
The business came to Teamed with what looked like a simple administrative question: could they just move the contractor onto payroll and carry on as normal? It is a fair question, and on the surface it looks like a quick fix. But it assumes that relabelling the relationship going forward also resolves whatever happened during the period it was misclassified. Those are two different problems. Treating them as one is the trap.
What Teamed identified, at principles level
Three things stood out. First, the relationship already had the hallmarks that employment tribunals look for: integration into the team, limited control over how the work was done, exclusivity, and a level of economic dependence typical of an employee rather than an independent business. Second, the risk was not only forward-facing. Historical exposure, unpaid entitlements, tax treatment, and potential liability if the arrangement were ever challenged, needed assessing on its own terms, separately from the go-forward fix. Third, the individual had earned real protections during that time that a contractor agreement never gave them, and the business had a chance to put that right rather than simply paper over it.
What was at stake
Left unresolved, this is the kind of arrangement that surfaces at the worst possible moment: a regulatory audit, an employee dispute, or a due diligence process ahead of a funding round or acquisition. The exposure sits quietly until someone asks the wrong question. Then it stops being a same-week fix and becomes a legal and financial problem.
What Teamed recommended
Teamed's recommendation was to formalise the relationship as genuine employment, not simply relabel it. That meant properly assessing the individual's role and seniority, structuring a compliant employment contract with the entitlements the law requires, and separately advising on how to handle the period before the conversion rather than treating the switch as a clean slate. The approach fixed the structure at the principle level, right classification, right entitlements, right documentation, before worrying about administrative speed.
Why this matters beyond New Zealand
This is not a one-country problem. Most developed labour markets, from the UK's tests for employment status to the EU's Platform Work Directive pushing member states toward presuming employment status by default for platform workers, are moving in the same direction: looking past what a contract says to what the relationship actually does. A contractor who is integrated, controlled, and economically dependent on one company looks like an employee to a regulator almost anywhere.
This is exactly what the Graduation Model is built for. Companies rarely start with the right structure in every market from day one. They start with a contractor because it is fast, the relationship deepens, and the risk profile changes long before anyone notices. The Graduation Model, contractor to EOR to entity, exists so that the transition happens on purpose, on a known timeline, with someone actively watching for the moment it needs to change, rather than being discovered by accident.
FAQs
Who is Teamed for?
Mid-market companies, 50-5,000 employees, employing internationally. The real qualifier is mindset: companies that value getting it right over getting it cheap. Businesses that want a set-it-and-forget-it platform, rather than an advisory relationship, are usually a better fit elsewhere.
How do you tell if a contractor should actually be an employee?
In most jurisdictions, tribunals look past the contract label to the real substance of the relationship. Key signals include exclusivity, integration into the team, the degree of control the company exercises over how the work gets done, and whether the individual carries genuine commercial risk. If a contractor works only for you, uses your systems, and reports to your managers over an extended period, the label on the contract is doing very little legal work.
Can you just move a misclassified contractor onto payroll and consider it fixed?
Changing the payroll code fixes the arrangement going forward, but it does not address what happened before the change. The period during which the relationship was, in substance, an employment relationship can carry its own liability, for unpaid entitlements, tax treatment, or potential claims. A proper conversion looks at both halves of the problem separately, not just the part that is easy to fix.
How long does it take to convert a contractor to a compliant employee?
Once employment terms are agreed by both parties and the individual completes onboarding, the conversion itself can be completed in about a week. Most of the time in these situations goes into agreeing the right role, seniority, and terms upfront, not into the administrative process once that agreement is reached.
What triggers contractor misclassification risk in the first place?
It is rarely a single decision. Misclassification risk tends to build gradually as a contractor's role expands beyond the original scope, becomes exclusive to one client, and starts to look, in practice, like a job rather than an engagement. The risk is highest for contractors who have worked with the same company for a long period, are embedded in day-to-day operations, and have no other clients.
When should a company move a converted employee to its own entity instead of keeping them on an EOR?
That decision usually comes down to Crossover Economics, the point at which running payroll and compliance through your own local entity becomes cheaper and more practical than employing through an EOR. For a single conversion, an EOR is usually the faster and lower-risk route. Once headcount in a market grows, the calculation shifts, and that is the conversation the Graduation Model is designed to have proactively, not reactively.
What happens if a business ignores a misclassification risk like this one?
It usually surfaces at the least convenient moment: a regulatory audit, an employee dispute, or a due diligence process ahead of a funding round or acquisition. At that point the fix is no longer a same-week administrative exercise. It becomes a legal and financial negotiation, often with penalties or backdated liabilities attached.
The honest answer, always
The global employment industry profits from companies not asking these questions. A contractor who has quietly become an employee is easy to ignore, right up until it isn't. Teamed exists to have that conversation before it becomes a crisis, tell you honestly what your structure needs to be, and then build it.
If a contractor relationship in your business has started to look like this one, bring it to the Situation Room. A named specialist will review your setup and tell you honestly what they see, whether that means an EOR conversion, a straight employment contract, or leaving things exactly as they are.
Talk to an Expert.