Blog
/
The PTO Feature That Could Turn Your Contractors Into Employees
Blog

The PTO Feature That Could Turn Your Contractors Into Employees

Offering paid time off to international contractors feels like a generous policy. Under most worker classification frameworks, it is evidence of an employment relationship. Here is why we deliberately left PTO tracking out of our contractor platform.

Updated on:

June 7, 2026

Ken O'Friel
CEO, Co-founder

TL;DR

  • PTO for contractors is one of the most common, well-intentioned features that creates legal exposure. In most jurisdictions, paid time off is treated as a benefit owed by an employer to an employee. Extending it to a contractor is direct evidence that the relationship is actually employment.
  • The risk is not theoretical. Worker classification cases in the UK (IR35), Germany (Scheinselbstandigkeit), France (URSSAF), Brazil, and India regularly turn on factors like PTO, fixed hours, exclusive engagement, and integration into company workflows. Reclassification triggers back taxes, mandatory benefits contributions, and penalties calculated retroactively across the entire engagement period.
  • Toku's contractor management platform does not include PTO tracking. This is a deliberate product design choice, not a feature gap. Tracking PTO inside the platform would create a written record that a worker engaged as a contractor was treated as an employee.
  • If you want to offer time off to your international contractors, there are two paths that do not create classification exposure: build a flat all-in rate that already prices in expected unavailability, or move the worker to an Employer of Record arrangement where they are correctly classified as an employee.
  • For workers who are genuinely contractors, the safe model is independence. They set their own hours. They invoice for work performed. They take time off without seeking approval, because they are not employees. The platform should not pretend otherwise.

Disclaimer: Toku provides compliance infrastructure and is not a law firm. This content is for informational purposes only and does not constitute legal or tax advice. Consult your legal counsel for jurisdiction-specific guidance.

The Question We Get on Almost Every Demo

The prospect is walking through the platform demo. They like what they see. They have around thirty contractors and they want to consolidate everything onto one system. Then they ask the question we hear on almost every call.

"Even if they are contractors, we want to give them time off. Can the platform track that?"

The honest answer is no. Not by accident. Not because we forgot to build it. We deliberately left PTO out of the contractor management platform, because tracking PTO for a contractor is one of the cleanest pieces of evidence a labor authority can use to reclassify that contractor as an employee. The question is good. The answer is harder. And the reason it is harder is the entire subject of this post.

What Misclassification Actually Looks Like

Worker classification is determined by the substance of the relationship, not the label on the contract. You can call someone a contractor in writing. You can sign a contractor agreement. You can pay them through a contractor invoicing platform. If the substance of how you work with them looks like employment, a labor authority can declare the relationship employment and apply employment law retroactively.

The exact tests vary by country. The US uses the IRS 20-factor test and the Department of Labor's economic realities test. The UK applies IR35. Germany evaluates Scheinselbstandigkeit, France applies URSSAF subordination tests, and most other jurisdictions have their own framework. The frameworks differ in detail but they look at broadly the same things: who controls the work, who controls the schedule, who provides equipment, whether the worker can take on other clients, whether the worker is integrated into the company's operational structure, and whether the worker receives benefits associated with employment.

PTO is in the last category. It is a benefit that employers provide to employees. Independent contractors do not get PTO because they are running their own businesses. They take time off whenever they want. They do not seek approval. They do not accrue days. When a company sets up a PTO tracker for a contractor, the company is treating them as an employee. Every labor authority in the world reads it that way.

Why We Deliberately Left PTO Out of the Platform

Most contractor management platforms include PTO tracking. We chose not to. The reason is straightforward. Every feature we build inside the contractor platform leaves a record. The platform itself becomes evidence in a classification dispute. If a labor authority subpoenas the platform and finds a PTO ledger for a worker who was supposed to be a contractor, that ledger is on the side of reclassification.

The same logic applies to other features that look helpful but create exposure. Fixed weekly hour tracking. Mandatory approval workflows for time off. Performance review cycles. Equipment provisioning tied to the worker's role. All of these are employer-like behaviors dressed up as platform features. Adding them to a contractor product makes the platform a liability rather than a protection.

What contractor management should do is the things contractors actually need. Send invoices. Receive payments. Generate tax documents. Track payment history. Onboard cleanly with proper contractor agreements. None of those features imply employment. They are the things a contractor relationship needs and nothing else.

Where Reclassification Bites Hardest

The jurisdictions where misclassification risk is highest tend to share two features. Strong worker-protection laws, and active enforcement regimes that look for foreign companies treating local workers as contractors.

Germany's Scheinselbstandigkeit framework is one of the strictest. A worker who economically depends on one company, takes direction from that company, and is integrated into its operations is presumptively an employee, regardless of the contract. The financial consequences include retroactive social security contributions, employer tax liability, and penalties.

The UK's IR35 rules require companies engaging contractors through personal service companies to assess whether the engagement is "inside IR35" (employment-like) or "outside IR35" (genuine contracting). If inside, employer taxes apply to every payment going back through the engagement.

France's URSSAF applies subordination tests. If a contractor takes orders, follows company-set hours, or is treated like an employee in any operational way, URSSAF can rule the relationship was employment and assess back social charges. Brazil, India, and several Latin American jurisdictions have aggressive frameworks of their own.

How to Offer Flexibility Without Creating Exposure

The instinct to be generous with international contractors is good. The execution matters. Two approaches work without creating classification risk.

The first is to build expected unavailability into the rate. A contractor invoicing $5,000 a month for full-time work knows that some weeks they will not be available. They price for that. The company is not paying for time off. The company is paying for output, and the rate already accounts for the contractor taking the time they need. No PTO ledger. No approval flow. No employer-like behavior.

The second is to move the worker to an employment arrangement if the relationship genuinely is employment. If you want to provide PTO, set fixed working hours, require exclusivity, integrate the worker into team rituals, and treat them like a member of the company, the honest move is to make them an employee. In countries where you have an entity, that is direct payroll. In countries where you do not, Employer of Record is the path.

Toku's Own Take on Why We Deliberately Removed This Feature - and What It Protects You From

The demo moment that prompted this article happens on almost every product walkthrough with a company managing around 30 contractors. The prospect asked, mid-demo: "Even if we are contractors, we have time off. Would that be possible to integrate that?" The rep's response was direct: "In order to make sure we're not getting into any potential misclassification setups, we specifically leave PTO out of the platform. That gives them evidence if they ever wanted to claim they were working as an employee but being hired as a contractor." That is a product design decision explained from the inside. No competitor article can include it because no competitor made the same decision for the same reason.

The South Africa prospect who described treating contractors "the same as if you're working on Fiverr with someone in another country" illustrates why this matters in practice. He was aware the arrangement was in a "gray area" but was treating it casually - no US 1099, no local equivalent, "up to them to report." The casualness coexists with practices that undermine the contractor classification: some of his contractors had fixed availability expectations and were deeply integrated into day-to-day operations. Adding PTO tracking to that arrangement would not have been a generous policy. It would have been additional evidence that the classification was wrong from the start.

The feature Toku did not build is one of the strongest signals that the platform was built by people who actually understand misclassification risk rather than people who were building a feature list. Most buyers do not think to ask about deliberately absent features. This one is worth knowing about before you choose a contractor management platform.

Frequently Asked Questions

Can I offer contractors paid time off without creating misclassification risk?

Not directly, no. PTO is treated as an employment benefit in nearly every jurisdiction. The alternatives are to build expected unavailability into a flat rate, or to convert the worker to an employee through direct payroll or an EOR arrangement.

What other features create misclassification risk besides PTO?

The main ones are fixed working hours, mandatory location requirements, exclusivity clauses, employer-provided equipment, integration into the company's org chart, performance review cycles, and approval workflows that govern when the contractor can or cannot work.

What happens if a labor authority reclassifies my contractor as an employee?

The consequences vary by jurisdiction but typically include retroactive payroll taxes, employer social security contributions, mandatory benefits contributions, penalties, and interest. The reclassification is usually applied across the entire engagement period.

If I want to give my contractors benefits, what is the cleanest path?

Convert the relationship to employment. If you have a local entity in the worker's country, run them on direct payroll. If you do not, use an Employer of Record so they are properly classified as an employee of the EOR's local entity.

Generosity Without Liability

The instinct to take care of the people working with you is the right one. The form that care takes is what matters. If you have a worker you want to bring onto proper employment terms, the Toku team can walk you through whether direct payroll, PEO, or EOR is the right fit for that specific role and country. The platform itself will not offer to track PTO for your contractors, and that is on purpose.

Table of contents
Share the article

Do you need an international token compensation plan?

Contact us