Employer of Record in Spain: Regional Variations in Collective Bargaining Agreements for 2026

You've just hired your first employee in Barcelona. The offer letter looks solid, the salary benchmarks check out, and your EOR provider confirms everything is compliant. Three months later, your CFO receives an invoice adjustment because the employee's role actually falls under a provincial convenio colectivo with a higher pay floor than the national sector agreement your provider assumed.

This scenario plays out constantly for mid-market companies expanding into Spain. The country's collective bargaining system operates across 17 Autonomous Communities, with agreements that can vary by sector, province, and even individual company. An Employer of Record that treats Spain as a single jurisdiction with uniform rules will eventually get caught by these regional variations.

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 your own presence in-country. Spain's CBA complexity is precisely the kind of challenge that separates advisory-led EOR providers from platform-only solutions.

What Actually Matters About Spain's CBAs in 2026

Spain has 17 regions plus Ceuta and Melilla. That's 19 different places where the rules can change. Your provider needs to know which collective bargaining agreement applies to each person you hire, based on exactly where they work.

To get Spain right, you need three things for every hire: where they'll work, what your business does there, and what they'll actually do day to day. Miss any of these and you'll get the wrong convenio, which means the wrong pay calculations.

Here's what trips up most audits: the job title on paper doesn't match what the person actually does. You hired a 'Marketing Manager' but they're doing sales work. The convenio knows the difference, and so will the auditor.

For multi-site Spanish workforces, the number of potentially relevant convenios rises with footprint because CBAs can exist at national, Autonomous Community, and provincial levels.

Provincial CBAs are particularly common in sectors with high local employer association density, including hospitality, retail, and logistics, which is why an EOR must validate province-by-province rather than assume a single national sector agreement applies.

What You'll Accomplish

By following this guide, you'll understand how to identify the correct collective bargaining agreement for any Spanish hire, evaluate whether your EOR provider can handle regional CBA variations, and build audit-ready documentation that satisfies both Finance and Legal. Expect to spend 15-20 minutes reading, with implementation time varying based on your current Spain footprint.

Before You Trust Anyone with Spain Payroll

Before evaluating EOR providers or mapping convenio requirements, you'll need clarity on three things. First, confirm the specific work locations for each Spanish employee, including whether they work remotely from a different province than your registered office. Second, identify your company's business activity code (CNAE) in Spain, as this determines which sector agreements apply. Third, document the actual job duties for each role, not just titles, since classification depends on function rather than nomenclature.

You'll also need access to your current employment contracts and payroll records if you're already operating in Spain. If you're working with an existing EOR, request their convenio determination documentation for each employee file.

First: Know Where Your People Are and What They Do

Start by creating a simple matrix of every Spanish employee or planned hire. For each person, record their principal work location at the province level, not just the Autonomous Community. Madrid, Barcelona, Valencia, and Seville each have distinct provincial agreements in many sectors that differ from broader regional or national CBAs.

Next, align each role to your company's primary business activity. A tech company hiring a customer support representative in Málaga might assume national tech sector agreements apply, but if that role primarily serves hospitality clients, the provincial hospitality convenio could take precedence based on functional scope rules.

The expected result from this step is a clear inventory showing employee name, province, sector alignment, and job function. This becomes the foundation for convenio determination.

Which Convenio Actually Applies (And Why It Matters)

Spanish CBAs operate in a hierarchy: national, Autonomous Community, provincial, and company-level agreements. The applicable convenio depends on territorial scope (where the work happens) and functional scope (what sector the work falls under), not employer preference.

For each role in your matrix, work through this sequence. Check whether a company-level CBA exists and has been validly negotiated with proper representational legitimacy. If not, identify whether a provincial convenio covers your sector in that specific province. If no provincial agreement exists, look for an Autonomous Community agreement. Finally, fall back to the national sector agreement only when no more specific territorial agreement applies.

A single role title like "Account Manager" often maps to multiple CBA categories with different pay floors depending on sector and province. Teamed's Spain benchmarking approach validates these variations during offer creation to prevent downstream compliance issues.

Where Most Providers Get Burned: Job Classifications

Once you've identified the applicable convenio, match each employee's actual duties to the agreement's professional group and job category definitions. This is where most compliance failures occur.

Spanish convenios define professional groups with associated pay tables, and misclassification risk arises when the employee's actual duties align to a higher category than the one used for payroll. If your marketing coordinator regularly manages external agency relationships and budget authority, they may fall into a higher classification than a coordinator role without those responsibilities.

Document the specific convenio article and classification table you're using, the employee's duties that justify that classification, and the resulting minimum pay floor. This documentation becomes essential for audit defence and invoice validation.

The Absorbability Trap (And How to Avoid It)

Spanish convenios frequently regulate which salary components are "absorbable/compensable" against future increases and which are strictly additive. Getting this wrong creates compliance risk that compounds over time.

When structuring offers, separate base salary from supplements and variable pay. Many convenios define specific supplements for seniority, shift work, or dangerous conditions that cannot be absorbed into base salary increases. If your employee's total compensation includes commissions or bonuses, verify whether the applicable convenio treats these as absorbable or additive.

In Spanish payroll operations, compliance risk increases when variable pay is used because many convenios define which supplements are absorbable versus strictly additive, according to Teamed's payroll QA findings. Structure payslips to clearly distinguish between components.

When to Revisit the Convenio (Before It Becomes a Problem)

CBA compliance isn't a one-time exercise. Several events should trigger a convenio re-evaluation: employee transfers between provinces, promotions that change job classification, remote work arrangements that shift the principal place of work, and convenio updates that introduce new pay tables or effective dates.

Changes in work location can change the applicable territorial convenio rules. An employee who relocates from Madrid to Barcelona may fall under a different provincial agreement, requiring contract amendments and payroll adjustments. Treat province changes as compliance events requiring fresh convenio determination.

Build a calendar for monitoring convenio renewals in your relevant sectors. When agreements update, your EOR must implement changes from the correct effective date and retain the updated convenio version used for calculation.

What a Good Provider Will Actually Show You in Spain

Here's the difference: a good provider gives you written documentation showing which convenio applies, why that classification was chosen, and who made the decision. Others give you a ticket number and hope you don't ask questions. If they can't show their reasoning, you're the one carrying the risk.

When evaluating providers, ask specific questions. Does the EOR provide written convenio determination and classification rationale for each employee file? Can they operationally support multi-site employment when employees work in different provinces? Do they have escalation access to Spanish labour counsel for edge cases like convenio conflicts or ultra-activity transitions?

If you're hiring in hospitality, retail, logistics, or contact centres, assume the local convenio will override the national one. These sectors have specific rules in almost every province. Ask your provider to prove they know the local agreements, not just the national defaults.

What Happens When Convenios Conflict or Expire?

Ultra-activity (ultraactividad) in Spanish collective bargaining keeps a CBA's terms in effect after its stated expiry date until replaced by a new agreement or a legally applicable fallback applies. This creates uncertainty for employers during negotiation periods.

When a convenio expires, your EOR should continue applying its terms while monitoring for replacement agreements. The risk comes when a new agreement introduces retroactive pay adjustments or classification changes. Your provider needs processes to implement these changes correctly and manage any back-pay obligations.

Company-level CBAs differ from sectoral agreements because they require a valid negotiation process with defined representational legitimacy. If your Spanish headcount grows to the point where works council formation becomes relevant, you may need to consider whether a company-level agreement makes strategic sense.

How to Check Your Provider Isn't Guessing

Request a sample employee file from your EOR showing the complete convenio determination workflow. A practical audit-ready minimum for Spain CBA governance is a maintained matrix of employee, work location, sector, convenio, classification, and pay minima. Teamed uses this structure as the standard artefact for cross-functional HR, Finance, and Legal sign-off.

Check that the file includes the specific convenio reference and publication date, the scope rationale explaining why this agreement applies, the classification mapping with supporting duty analysis, the pay table snapshot showing minimum floors, and an effective-date log for any changes.

No documentation means you'll find out they guessed when it matters most: during an audit, when an employee challenges their classification, or when the labour inspector shows up asking questions.

When the Invoice Suddenly Changes

When invoices don't match expected costs, the most common cause is mid-period convenio updates that introduced new pay floors or supplements. Request the specific convenio version and effective date your EOR used for calculation.

If an employee disputes their classification, compare their actual duties against the convenio's professional group definitions. The resolution depends on function, not title, and may require contract amendments if the classification was incorrect.

For multi-province teams experiencing inconsistent treatment, verify that your EOR is performing province-specific convenio determination rather than applying a single national assumption. This is particularly important in sectors like hospitality and retail where provincial agreements are common.

When to Stop Using EOR and Set Up Your Own Spanish Entity

Spain falls into Tier 2 (moderate complexity) in Teamed's Graduation Model framework, with an entity transition threshold of 15-20 employees for native language operations or 20-30 employees when operating in a non-native language. The Graduation Model is Teamed's proprietary framework for guiding companies through sequential employment model transitions, providing continuity through a single advisory relationship and avoiding the disruption of switching providers at each stage.

Choose an EOR when you need to hire in under 6-8 weeks without incorporating a Spanish entity and you still need local compliance coverage for convenios, payroll, and statutory filings. Choose a Spanish entity when you expect sustained headcount across multiple provinces and need direct control over CBA negotiations, works council strategy, or union engagement.

The economics shift when your annual EOR costs multiplied by expected years exceed entity setup cost plus ongoing annual costs. For Spain, factor in the complexity of managing multiple provincial convenios when calculating the administrative burden of direct employment.

How to Stop This Becoming a Recurring Spain Problem

If you're currently operating in Spain with incomplete convenio documentation, start by auditing your existing employee files against the standards outlined here. Identify gaps in classification rationale, missing convenio references, or provinces where determination hasn't been validated.

For companies planning Spain expansion, build convenio determination into your hiring workflow from day one. Require written documentation before any offer goes out, and establish clear triggers for re-evaluation when circumstances change.

If your current EOR can't demonstrate the capabilities described here, you're not getting the compliance confidence you're paying for. The right structure for where you are means having a provider who understands that Spain isn't one jurisdiction but seventeen, each with its own collective bargaining landscape.

Want to know if your Spain setup will survive an audit? Book your Situation Room. Bring your current convenio documentation (if you have any) and we'll tell you where the risks are and exactly what to do about them. Whether that includes working with us or not.

‍

Hiring Remote Workers in Banking, Aviation, and Telecom: What the 2026 Canada Labour Code Changes Mean

Your VP of People Operations just approved a remote hire in Calgary for your Toronto-based telecom company. Simple enough, right? Except the 2026 Canada Labour Code amendments have changed the compliance landscape for federally regulated employers, and that "simple" hire now requires updated policies, new documentation, and a clear understanding of which rules actually apply.

Federally regulated employers in banking, aviation, telecommunications, and interprovincial transportation face a unique challenge. The Canada Labour Code governs your employment relationships regardless of which province your remote workers call home. But the 2026 updates have introduced new obligations around flexible work arrangements, harassment prevention, and termination procedures that directly affect how you hire, onboard, and manage distributed teams.

This guide translates those regulatory changes into a practical remote hiring workflow. You'll walk away with a jurisdiction triage method, step-by-step compliance actions, and decision logic for the scenarios that keep HR leaders awake at night: interprovincial moves, cross-border requests, and the contractor-versus-employee question that never quite goes away.

Quick Facts: 2026 Canada Labour Code Remote Hiring Compliance

Federally regulated private-sector employers represent approximately 5.8% of Canada's workforce, meaning most Canadian remote hires fall under provincial jurisdiction unless the employer's core undertaking is federal in scope.

Plan for 3-8 internal stakeholders to touch a single remote hire in a regulated context, spanning HR, Legal, Payroll, Finance, IT/Security, and the hiring manager.

Expect 10-25 distinct compliance artifacts per remote hire, including offer letters, remote-work addenda, policy acknowledgements, security attestations, and payroll forms.

Assume 5-15% annual location churn in distributed teams, where employees relocate or work temporarily from another jurisdiction, triggering re-triage and updated documentation.

Use a 15-minute per-hire compliance triage target for remote hiring, covering jurisdiction, classification, location, and data security gates.

Budget 2-6 weeks to stand up compliant cross-border remote employment when hiring from outside Canada into a Canadian employer group.

What You'll Accomplish

By following this guide, you'll build a repeatable remote hiring compliance process aligned with the 2026 Canada Labour Code requirements. The workflow covers pre-hire classification through ongoing management and offboarding, with clear stop/go gates at each stage.

Time estimate: 15-20 minutes to read and understand the framework, then 15 minutes per hire to execute the triage and documentation process.

Prerequisites: Access to your company's current employment policies, remote work agreements, and payroll registration details. You'll also need clarity on whether your organisation qualifies as a federally regulated undertaking under the Canada Labour Code.

How Do You Confirm Whether the Canada Labour Code Applies to Your Remote Role?

A federally regulated employer is a Canadian employer whose business activities fall under Parliament's jurisdiction. This includes banks, telecommunications companies, interprovincial transportation operators, airlines, and certain Crown corporations. Part III of the Canada Labour Code becomes your baseline for employment standards regardless of where your employee physically works.

Here's the triage question that matters: Does your organisation's core undertaking fall within federal jurisdiction? If you're a bank headquartered in Ontario hiring a remote worker in British Columbia, the Canada Labour Code applies. If you're a provincially incorporated software company hiring that same BC worker, provincial employment standards govern instead.

The 2026 amendments haven't changed this fundamental jurisdictional test. What they have changed is your obligations once you've confirmed federal jurisdiction applies. The flexible work arrangement provisions, updated harassment and violence prevention requirements, and enhanced termination notice rules all affect remote hiring workflows specifically.

The Jurisdiction Triage Checklist

Step 1: Confirm your employer status. Review your corporate registration and primary business activities against the federal undertaking categories in the Canada Labour Code.

Step 2: Assess the role's integration. Is the remote worker performing work that's functionally integrated into your federal undertaking? A software developer building your banking platform is integrated. A contractor providing one-off marketing services may not be.

Step 3: Document the determination. Create a jurisdiction memo for each hire that records your analysis. This becomes your audit trail if questions arise later.

Step 4: Register for payroll in the worker's province. Even under federal jurisdiction, you'll need provincial payroll tax registrations for workers in each province.

What Changed in 2026 and Why It Matters for Remote Hiring

The 2026 Canada Labour Code amendments introduced several provisions that directly affect remote employment relationships. Understanding what changed helps you identify which policies need updating and which hiring practices require adjustment.

Flexible Work Arrangement Rights

Employees can now formally request flexible work arrangements, including remote work, schedule changes, and modified hours. Employers must respond in writing within 30 days and provide reasons if declining. For remote hiring, this means your offer letters and employment agreements should address remote work terms upfront rather than treating them as informal arrangements.

The practical impact: You need documented remote work policies that specify eligibility criteria, approval processes, and the conditions under which arrangements can be modified or revoked. Ad hoc remote work approvals create compliance exposure when employees later claim they were denied flexible arrangements without proper justification.

Harassment and Violence Prevention Updates

The Labour Program reminded federally regulated employers in January 2026 about compliance requirements for harassment and violence prevention policies. For remote workers, this means your policies must address how investigations occur when employees work from home, how reporting mechanisms function across distributed teams, and how you'll ensure remote workers receive the same protections as on-site staff.

Termination and Notice Requirements

Updated termination provisions require specific notice periods and job planning committee requirements for larger workforce reductions. Remote workers are subject to the same protections, which means your offboarding procedures need to account for equipment retrieval, final pay timing, and documentation requirements regardless of where the employee works.

Step 1: Pre-Hire Classification - Employee or Contractor?

Before you draft an offer letter, you need to determine whether the role should be structured as employment or an independent contractor arrangement. This decision has significant compliance implications under the Canada Labour Code.

An employee is a worker who is economically dependent on the engager and integrated into the engager's business operations. The employer becomes responsible for statutory employment standards, payroll withholdings, and protected leave administration. A contractor is an independent business person who controls how and when work is performed and bears financial risk.

The classification test focuses on control and integration. If the worker will have set hours, ongoing supervision, and core operational responsibilities indistinguishable from employees, you're looking at an employment relationship regardless of what the contract says.

Red flag indicators requiring written justification: When a worker uses employer-provided equipment plus employer-set working hours, you're in high-likelihood reclassification territory. Teamed's contractor governance controls recommend requiring a written contractor independence rationale when both indicators are present.

Choose an employee model when the worker will have set hours, ongoing supervision, and core operational responsibilities. Choose a contractor model only when the worker can demonstrate business independence through multiple clients, control over schedule and methods, and the ability to subcontract.

Step 2: Job Posting and Selection Compliance

Your job posting is the first compliance touchpoint in the remote hiring workflow. The 2026 requirements intersect with provincial pay transparency laws that are rolling out across Canada, creating a layered compliance environment.

For federally regulated employers, job postings should clearly indicate whether the role is remote, hybrid, or on-site. If you're open to candidates across multiple provinces, your posting should reflect the salary range applicable to each location where pay transparency requirements exist.

Document your selection criteria and interview process. While the Canada Labour Code doesn't mandate specific hiring procedures, maintaining records of your selection rationale protects against discrimination claims and demonstrates good-faith compliance with human rights obligations.

Expected result: A job posting that accurately describes the remote work arrangement, complies with applicable pay transparency requirements, and creates a documented selection process.

Step 3: Offer Letter and Remote Work Terms

Your offer letter for a remote worker needs to address elements that wouldn't appear in a traditional on-site employment agreement. The 2026 flexible work arrangement provisions make it important to document remote work terms at the outset rather than treating them as informal understandings.

A remote work agreement addendum is a contract attachment that sets remote-work location, hours and availability expectations, equipment and expense rules, confidentiality and security requirements, and compliance responsibilities. This creates auditable evidence of lawful working-time and recordkeeping practices.

Essential Offer Letter Elements for Remote Workers

Work location specification: Name the province where the employee will primarily work. This affects payroll registration, workers' compensation coverage, and statutory holiday entitlements even under federal jurisdiction.

Hours and availability: Specify expected working hours and any core hours when the employee must be available. The Canada Labour Code's hours of work provisions apply to remote workers, and you need documented expectations to manage overtime compliance.

Equipment and expenses: Clarify what equipment you'll provide, what expenses you'll reimburse, and the employee's obligations for maintaining a suitable home workspace.

Location change approval: Include a clause requiring advance approval for any change in primary work location. This creates a compliance gate for the inevitable "I'm moving to another province" conversation.

Expected result: An offer letter package that establishes clear remote work terms, creates documentation for hours of work compliance, and includes a location change approval requirement.

Step 4: Onboarding and Required Notices

Remote worker onboarding requires the same statutory notices as on-site employment, plus additional documentation specific to distributed work arrangements. The 2026 harassment and violence prevention requirements make policy acknowledgements particularly important.

Onboarding Compliance Checklist

• Employment standards notice: Provide the required Canada Labour Code employment standards information.
• Harassment and violence prevention policy: Distribute your policy and obtain written acknowledgement.
• Remote work policy acknowledgement: Document the employee's agreement to your remote work terms.
• IT security attestation: Confirm the employee understands data handling and security requirements.
• Equipment inventory: Document all employer-provided equipment and the employee's responsibility for its care.
• Timekeeping setup: Establish the method for tracking hours worked, including overtime pre-approval procedures.
• Payroll forms: Complete federal and provincial tax forms based on the employee's work location.

Teamed's compliance checklist structure for audit-ready onboarding typically includes 10-25 distinct artifacts per remote hire. The specific number depends on your industry, the role's access to sensitive data, and whether the employee will work across multiple jurisdictions.

Expected result: A complete onboarding file with all required notices, policy acknowledgements, and documentation establishing the remote work arrangement.

Step 5: Ongoing Management - Hours, Overtime, and Availability

Managing remote workers under the Canada Labour Code requires documented systems for tracking hours and managing overtime. You can't rely on physical observation, so your compliance depends on policies, timekeeping tools, and clear expectations.

The Canada Labour Code's standard hours provisions apply to remote workers. Employees are generally entitled to overtime pay after 8 hours in a day or 40 hours in a week, with some variations based on averaging agreements or modified work schedules.

Treat any role with recurring overtime risk as a finance-impact role. A sustained 5 hours of overtime per week at time-and-a-half equates to roughly 13% additional straight-time pay over a year. Teamed uses this as a CFO-friendly screening calculation for working-time exposure.

Availability Expectations and Right-to-Disconnect

While Canada doesn't have a federal right-to-disconnect law equivalent to Ontario's provincial requirement, the 2026 flexible work arrangement provisions create an expectation that employers will clearly communicate availability requirements. Document when employees are expected to be available, how quickly they should respond to communications, and any core hours requirements.

Expected result: Documented timekeeping procedures, overtime pre-approval processes, and clear availability expectations that create auditable compliance records.

What Happens When a Remote Employee Moves Provinces?

This scenario generates more compliance questions than almost any other remote work situation. An employee hired to work remotely from Ontario announces they're relocating to Alberta. What changes?

For federally regulated employers, the Canada Labour Code continues to apply regardless of the move. Your employment standards baseline doesn't change. But several administrative elements require attention.

Payroll registration: You may need to register for payroll tax remittances in the new province if you don't already have employees there.

Workers' compensation: Coverage requirements vary by province. Confirm your registration status and any reporting obligations.

Statutory holidays: The Canada Labour Code specifies federal statutory holidays, but some provinces have additional holidays that may affect your operations.

Employment agreement update: Document the location change and confirm the employee's new work address for records purposes.

Treat location-change requests as a compliance event requiring re-triage and updated documentation. Teamed's remote-work governance recommendations assume 5-15% annual location churn in distributed teams, so building a repeatable process for these situations pays dividends.

When Should You Escalate Cross-Border Remote Work to Legal Counsel?

Cross-border remote work, where a Canada-based employer has a worker physically located outside Canada, introduces complexity that exceeds standard HR decision-making. Choose legal review when the employee will be physically outside Canada for more than 183 days in any 12-month period, because this is a common tax residency and permanent-establishment screening threshold.

The issues multiply quickly: immigration status in the destination country, tax residency implications, social security coordination between countries, data export restrictions under Canadian privacy law, and local employment law requirements in the worker's location.

An Employer of Record arrangement may be appropriate when the worker will be located outside Canada and you don't have a local entity or payroll infrastructure. The EOR provides a local employing structure and statutory payroll compliance while you retain day-to-day direction of the work.

Teamed's cross-border hiring triage guidance recommends budgeting 2-6 weeks to stand up compliant cross-border remote employment, covering work authorization pathways, payroll and tax setup, and local contract terms.

Compliance Ownership Map: Who Does What?

Clear ownership prevents the compliance gaps that occur when everyone assumes someone else is handling a requirement. For remote hiring in federally regulated sectors, responsibilities typically distribute across multiple functions.

HR/People Operations: Job posting compliance, offer letter preparation, onboarding coordination, policy distribution, and ongoing employee relations.

Legal/Compliance: Jurisdiction triage documentation, contractor classification review, cross-border escalation, and policy updates for regulatory changes.

Payroll/Finance: Provincial payroll registration, tax withholding setup, overtime tracking and payment, and workers' compensation registration.

IT/Security: Equipment provisioning, security attestation collection, data handling training, and access management for remote systems.

Hiring Manager: Role requirements definition, interview process execution, and ongoing performance management.

Teamed's operating model benchmarks for mid-market teams show 3-8 internal stakeholders typically touch a single remote hire in a regulated context. Mapping ownership explicitly reduces cycle time and prevents dropped handoffs.

Troubleshooting Common Remote Hiring Issues

The employee wants to work from a different location than originally agreed. Treat this as a compliance event. Review your location change approval clause, assess any payroll or workers' compensation implications, update your records, and document the approval.

You're unsure whether a role should be employee or contractor. Apply the control and integration test. If you're still uncertain, err toward employment. The compliance cost of misclassifying an employee as a contractor significantly exceeds the cost of properly employing someone who could have been a contractor.

A remote worker is logging excessive overtime. Review your timekeeping records and overtime pre-approval process. If overtime wasn't pre-approved, you may still owe the pay, but you can address the procedural issue going forward. Document the conversation and reinforce your overtime policy.

An employee requests to work from outside Canada temporarily. Assess the duration and purpose. Short trips may not trigger compliance issues, but extended stays require the cross-border analysis described above. When in doubt, escalate to counsel before approving.

Next Steps: Building Your Remote Hiring Compliance System

The 2026 Canada Labour Code changes don't fundamentally alter how federally regulated employers hire remote workers. They do, however, raise the stakes for documentation, policy clarity, and systematic compliance processes.

Start by auditing your current remote work policies against the flexible work arrangement requirements. Update your offer letter templates to include remote-specific terms. Build a jurisdiction triage checklist that your team can execute in 15 minutes per hire. And establish clear ownership for each compliance element across HR, Legal, Payroll, and IT.

For mid-market companies managing remote teams across multiple provinces and employment models, the challenge often isn't understanding the rules. It's building systems that apply those rules consistently across every hire. If you're piecing together advice from multiple vendors with conflicting incentives, or making six-figure employment decisions without dedicated strategic guidance, there's a better approach.

Talk to the experts at Teamed to see how unified global employment operations can bring clarity to your remote hiring compliance, whether you're managing federally regulated Canadian teams or expanding across borders.

Washington State Worker Classification: The Reality Check You Need Before That First Contract

You've found the perfect software developer in Seattle. They want to work as a 1099 contractor. Your hiring manager says it's simpler, your CFO likes the cost savings, and the candidate prefers the flexibility. Everyone's happy.

Until Washington's Department of Labor & Industries (L&I) decides your "contractor" is actually an employee. Now you're scrambling to cover back premiums and penalties while your CFO asks why nobody caught this earlier.

Washington State starts with the assumption that every worker is an employee until you prove otherwise. What makes it particularly tricky is that L&I and the Employment Security Department (ESD) look at different things when they evaluate the same worker. You can pass one test and fail the other. Mid-market companies get caught in this trap all the time, especially when they're managing contractors across multiple states and trying to keep track of different rules everywhere.

What Usually Triggers Classification Questions in Washington

• One worker complaint can trigger a full review of your contractor relationships. It happens more often than you'd think.
• A proper classification review needs answers about control, tools, substitution rights, how you pay them, and how integrated they are in your operations. If you can answer these questions clearly, you'll know where you stand.
• If your contractor doesn't have business registration, their own insurance, or other clients, you're already in risky territory. These are the first things agencies look for.
• Your biggest risk usually comes from long-term contractors doing core work, not the specialist you bring in for a specific project. The more integrated they are, the harder it is to defend contractor status.
• Keep your classification documentation for at least 6 years. When agencies come asking about past relationships, you'll need those records to show your reasoning.

What's the Difference Between an Employee and Independent Contractor in Washington?

In Washington, the default assumption is that anyone working for you is an employee covered by wage laws, unemployment insurance, and workers' comp. You control their schedule, their methods, and their priorities.

An independent contractor runs their own business and can prove it. They decide how to do the work, when to do it, and they have the infrastructure of a real business. Washington agencies will test this independence from multiple angles.

Washington starts with employee status as the default. You have to prove contractor status with evidence, not just paperwork. A contract titled "independent contractor agreement" won't save you if the working relationship says otherwise.

The real test examines the working relationship itself. Does the worker set their own hours? Do they provide their own tools? Can they work for other clients? Do they invoice for outcomes rather than time? Washington agencies look at these facts, not the paperwork.

How Do Washington L&I and ESD Evaluate Worker Status Differently?

Two different agencies, two different tests. L&I looks at one set of factors for workers' comp, while ESD weighs things differently for unemployment insurance.

Washington L&I (Department of Labor & Industries) administers workers' compensation and evaluates whether a worker must be covered under an employer's industrial insurance account. L&I focuses heavily on control factors and whether the worker operates an independently established business.

Washington ESD (Employment Security Department) administers unemployment insurance and determines whether payments to a worker are "employment" subject to unemployment tax reporting. ESD applies its own statutory test that emphasises similar factors but weighs them differently.

You can satisfy L&I and still have problems with ESD. Take a construction subcontractor with their own LLC and multiple clients. L&I might be fine with that, but if they work only for you during busy seasons, ESD could see it differently.

Keep one complete file showing how you evaluated the relationship against both L&I and ESD requirements. When questions come up, you'll need to show your thinking for each agency's test.

Employee or Contractor: How Washington Agencies See the Difference

The Factors That Actually Move the Needle in Washington

Not all factors are equal. Control and independent business operations matter most. Start there, then look at integration and economic dependence.

Control Over Methods and Schedule

Does the business direct how the work gets done, or just what outcome is expected? Employee-style arrangements involve manager-set priorities, performance reviews, and scheduling requirements. Contractor arrangements rely on outcome-based scopes with the worker controlling methods.

Tools, Equipment, and Workspace

Who provides the laptop, software licenses, office space, and specialised equipment? Employees typically use employer-provided resources. Contractors invest in their own tools and infrastructure.

Economic Independence

Can the worker realise profit or loss based on how they run the engagement? Do they market services to multiple clients? Contractors who work exclusively for one company, lack their own business infrastructure, and cannot realistically pursue other clients look like employees regardless of what the contract says.

Integration Into Business Operations

Is the worker performing core, ongoing work that's materially integrated into the company's primary service delivery? Or are they completing a discrete, outcome-based project? The more integrated the role, the stronger the employee classification argument.

Right of Substitution

Can the worker send someone else to do the job without your approval? True contractors can substitute personnel or subcontract. Employees cannot delegate their work to others.

Before You Sign That Contract: A Washington Reality Check

Run through these questions based on how the relationship will actually work, not what the contract says. Be honest with yourself. For a structured assessment, try this classification quiz.

Multiple "yes" answers mean you're describing an employee relationship. The specific combination matters more than the count. If you're seeing red flags, it's worth getting a second opinion before moving forward.

When Washington Decides Your Contractor Is Actually an Employee

You call them a contractor. Washington calls them an employee. Now you owe back taxes, premiums, and penalties. That's misclassification in a nutshell.

The bills come from everywhere at once. L&I wants workers' comp premiums. ESD wants unemployment insurance. The worker might file wage claims.

Back Premiums and Taxes

L&I can assess back workers' compensation premiums for the entire period of misclassification, plus interest. ESD can demand unpaid unemployment insurance contributions going back years. Both agencies can audit your entire contractor population, not just the worker who triggered the inquiry.

Penalties and Interest

Washington imposes penalties on top of back premiums. The longer the misclassification continued, the larger the penalty calculation—L&I assessed more than $118.2 million in premiums, penalties, and interest against businesses in fiscal year 2025.

Wage-and-Hour Claims

Misclassified workers can pursue claims for unpaid minimum wage, overtime, meal and rest breaks, and other protections they should have received as employees. These claims can extend back years and include attorney's fees.

Defence Costs

Even if you win, you lose. Your HR team spends months gathering documents. Finance rebuilds payment records. Legal fees pile up. The real cost isn't just the penalties, it's everything that stops while you deal with it.

Think about your total exposure this way: back premiums and taxes, penalties that compound over time, potential wage claims, and the cost of defending it all. It adds up fast.

What This Looks Like for Real Washington Roles

Let's look at how these rules play out with actual roles you might be hiring for in Washington.

1099 Software Developer

A developer who works remotely, sets their own hours, uses their own equipment, invoices monthly for completed features, maintains an LLC, carries professional liability insurance, and works for multiple clients simultaneously presents strong contractor indicators. The same developer who works on-site, attends daily standups, uses company-provided equipment, receives regular paychecks, and works exclusively for one company for 18 months looks like an employee.

Construction Labourer

Washington construction carries heightened scrutiny, contractors must pass all 7 parts of the exemption test to avoid workers' comp coverage. A labourer who shows up when the general contractor says, uses provided tools, works under direct supervision, and has no other clients is almost certainly an employee. A licensed subcontractor with their own crew, equipment, insurance, and multiple active projects has a stronger contractor argument.

Owner-Operator Trucking

Trucking classification depends heavily on control factors. Does the driver own or lease the truck? Who controls routes, schedules, and customer relationships? Can the driver haul for other companies? Washington examines the economic reality, not just the lease agreement.

Salon Booth Rental

Booth renters who set their own prices, maintain their own client lists, control their schedules, and pay fixed rent for space typically qualify as contractors. Stylists who work assigned shifts, use salon pricing, and cannot build independent client relationships look like employees.

Home Healthcare

Healthcare workers face particular scrutiny in Washington. Caregivers who work regular schedules, receive training, follow care plans created by the agency, and cannot substitute other workers are typically employees regardless of 1099 paperwork.

What to Keep on File So You're Not Scrambling Later

When L&I or ESD comes calling, you need to show your homework fast. That means having one file with everything that shows why you classified someone as a contractor.

For each contractor, you'll want their contract, business registration, insurance certificates, invoices showing project-based billing, and evidence they work for other clients. That's usually about 8 to 12 documents that prove the business relationship.

What to Collect

Start with the basics: their signed contract with specific deliverables, not just hourly work. Add their business registration, whether that's an LLC or sole proprietorship. Get copies of their business insurance. Keep invoices that show project billing, not timesheets. If they have marketing materials or other client references, file those too. A simple attestation about their independent business doesn't hurt either.

What to Avoid

Some documents scream "employee" to auditors. If you're giving contractors employee handbooks, making them request time off, setting their hours, doing performance reviews, or giving them company email addresses, you're treating them like staff. Agencies notice.

Process Controls

Your day-to-day operations need to match your paperwork. Don't require contractors at all-hands meetings. Don't offer them benefits. Don't put them through your disciplinary process. If it walks like an employee and talks like an employee, agencies will call it an employee.

When to Stop Fighting It and Just Hire an Employee

If you're controlling their schedule and telling them how to do the work, they're an employee. If they're doing the same core work as your team day after day, they're an employee. If they depend on you for their income and don't have a real business of their own, they're an employee. Stop trying to make it something else.

Most of the roles companies try to fill with contractors should be employees. The money you save on payroll taxes vanishes the moment an audit hits. It's just not worth the risk for core, ongoing work.

For mid-market companies expanding into Washington, the decision often comes down to operational reality. When converting contractors to employees becomes necessary, proper compliance steps matter.

What About EOR as an Alternative to Washington Contractors?

An EOR makes sense when you need someone to be an employee but don't have a US entity. They handle the payroll taxes, unemployment insurance, and workers' comp while you manage the actual work. Clean and compliant.

An EOR becomes the legal employer for payroll and statutory programs while you direct the work. This eliminates misclassification risk entirely because the worker is properly employed, just not by you directly.

For European and UK companies hiring in Washington, you're dealing with L&I for workers' comp, ESD for unemployment, plus Washington's specific wage rules. An EOR handles all of this through one relationship instead of you juggling multiple requirements.

The progression usually looks like this: contractors when you're testing a market, EOR when roles become permanent but you're not ready for an entity, then your own entity when the numbers make sense. What matters is having consistent advice through each stage, not different vendors pushing their preferred model.

Frequently Asked Questions

How does the IRS determine if someone is an independent contractor or an employee?

The IRS uses a common law test examining behavioural control, financial control, and relationship type. However, passing the IRS test doesn't guarantee you'll pass Washington's state-specific tests. Washington L&I and ESD apply their own statutory frameworks, and a worker can be a contractor for federal purposes while being an employee under Washington law.

Is it better to be paid as an employee or independent contractor?

It depends on your situation. Employees receive protections including minimum wage, overtime, workers' compensation coverage, and unemployment insurance eligibility. Contractors have more flexibility and potential tax deductions but bear all tax obligations, lack employment protections, and must maintain their own insurance. The classification isn't a choice, though. It's determined by the actual working relationship, not preference.

What triggers a Washington classification audit?

Washington agencies can initiate classification reviews based on worker-initiated claims such as unemployment claims or workers' compensation claims, making one adverse event a realistic trigger for an inquiry. Audits can also result from routine compliance reviews, tips from competitors, or patterns in tax filings that suggest misclassification.

If You're Still on the Fence

Washington worker classification isn't about finding loopholes or structuring paperwork to avoid employee status. It's about honestly evaluating each working relationship and classifying it correctly from the start.

Companies that stay out of trouble do three things well. They document why they classified someone as a contractor. They make sure daily operations match what the paperwork says. And when they're not sure, they ask for help before signing anything.

Managing contractors gets harder when you're in multiple states. Washington wants one thing, California wants another, New York has its own rules. Without someone who sees the whole picture, you end up with different vendors telling you different things while you're trying to make expensive decisions.

If you're not sure about classification in Washington, we can walk through the facts with you. A conversation now saves months of cleanup later.

Does the USA Have a Temporary Foreign Worker Program? The Reality in 2025

Your UK specialist needs to be in the States for six months. Your CFO wants to know if there's a temporary worker program you can use. Here's the thing: there isn't one. Not like Canada or Australia have, anyway. The U.S. runs eleven different visa categories split between three federal agencies, and each one has its own rules.

When you're already juggling contractors in one system and EOR employees in another, this mess just adds to the chaos. You can't just "apply for a temporary worker permit." You have to figure out which of eleven visa categories fits, check if the Department of Labor needs to sign off first, then work through USCIS and the State Department. Every handoff is another chance for delays that push back your start date.

This guide maps the U.S. temporary worker system into a practical decision framework. You'll understand which agency does what, when DOL certification is required, and how to identify the right pathway based on your specific hiring scenario.

The Numbers That Matter for Your Timeline

The H-1B cap is 65,000 new visas per fiscal year plus an additional 20,000 for workers with qualifying U.S. master's degrees or higher, making H-1B a quota-limited pathway for many private-sector employers. The H-2B program is capped at 66,000 visas per U.S. fiscal year, split as 33,000 for the first half and 33,000 for the second half, creating predictable seasonal availability constraints. L-1A status is generally granted for up to 3 years initially with a maximum of 7 years total, while L-1B is generally granted for up to 3 years initially with a maximum of 5 years total. The maximum initial period of stay is typically up to 3 years for H-1B and up to a cumulative maximum of 6 years in H-1B status. Under the Visa Waiver Program, eligible citizens can enter the U.S. for up to 90 days for business visitor activities without a visa, but this category does not authorise productive U.S. employment.

What You'll Know Before You Brief Your CFO

By the end of this guide, you'll be able to identify which U.S. temporary worker visa category applies to your hiring situation, understand the three-agency workflow that governs all temporary worker pathways, and avoid the most common compliance failures that trip up mid-market companies expanding into the U.S. market. Expected time to work through this framework: 20-30 minutes for initial pathway identification, with detailed planning requiring additional consultation.

Before You Pick a Visa, Get These Facts Straight

Before selecting a temporary worker pathway, you need clarity on several factors. First, define the nature of the work: is it agricultural, seasonal non-agricultural, a specialty occupation requiring a degree, an intra-company transfer, or a cultural exchange? Second, establish the expected duration and whether the role is genuinely temporary or could become permanent. Third, confirm the worker's qualifications, including education, prior employment with related entities, and citizenship status. Finally, determine whether your company has the required employer-employee relationship with the worker.

If you're operating in 5-15 countries and managing U.S. operations across states, write down whether each U.S. trip is for "visitor activities" or actual work. Sounds basic, but mixing these up is how people get turned away at the border.

So Does the U.S. Actually Have One Temporary Worker Program?

The United States does not have one single "Temporary Foreign Worker Program" like Canada or Australia. Instead, it operates multiple temporary (nonimmigrant) worker visa programs administered across agencies, primarily the Department of Labor (DOL), U.S. Citizenship and Immigration Services (USCIS), and the Department of State. A temporary foreign worker program in the U.S. is a practical umbrella term for multiple nonimmigrant visa categories that allow foreign nationals to work in the United States for a time-limited purpose under rules enforced by several federal agencies rather than a single unified program.

This multi-agency structure means employers must navigate different requirements depending on which visa category applies. Some pathways require DOL labour certification before USCIS will accept a petition. Others bypass DOL entirely. Understanding this distinction is the first step toward selecting the right pathway.

Here's the Order of Operations (and Where It Usually Breaks)

The U.S. temporary worker system follows a three-agency workflow: DOL certification (when required), USCIS petitioning, and State Department visa issuance. Each step has distinct approval criteria and processing timelines.

First Check: Do You Need DOL Approval?

The Department of Labor's role varies by visa category. For H-2A (agricultural) and H-2B (non-agricultural seasonal) visas, employers must obtain a temporary labour certification from DOL before filing with USCIS. This certification confirms that no qualified U.S. workers are available and that hiring foreign workers won't adversely affect wages and working conditions of similarly employed U.S. workers.

A U.S. labour certification for temporary workers is a DOL approval that an employer may need before filing an immigration petition, typically to confirm a temporary labour need and that hiring foreign workers will not adversely affect U.S. workers' wages and working conditions. For H-1B specialty occupation visas, employers file a Labour Condition Application (LCA) with DOL, but this is a less intensive process than full labour certification.

L-1 transfers and O-1 extraordinary ability skip DOL entirely. That saves weeks, but the evidence requirements can still be heavy.

Next, USCIS Decides If the Role and Person Qualify

USCIS Form I-129 is an employer-filed petition used to request many temporary worker classifications, including H-1B, H-2A, H-2B, O-1, P, Q, and some L classifications. An approved I-129 is generally required before a worker can apply for a visa stamp at a U.S. consulate. The employer, not the worker, files this petition. USCIS adjudicates whether the position qualifies for the requested classification and whether the worker meets eligibility requirements.

Processing times vary significantly by category and service centre. Premium processing is available for some categories, reducing adjudication to 15 business days for an additional fee. Standard processing can take several months.

Then the Consulate Issues (or Denies) the Visa

Consular visa issuance is the U.S. Department of State process in which a worker outside the United States applies for a visa stamp after USCIS approves the employer petition. The visa stamp is used to request admission at a U.S. port of entry. Workers already in the U.S. in valid status may be able to change status without leaving the country, but most workers abroad must attend a consular interview.

At the Border, CBP Has the Last Word

CBP admission is the U.S. Customs and Border Protection process that determines whether a worker is allowed to enter the United States in the requested classification and for what authorised period. The period of stay granted on entry (recorded on the I-94) can differ from the petition's requested dates. The I-94 record, not the visa stamp, controls the worker's authorised period of stay inside the United States.

Remember: the visa gets you to the door. The I-94 decides how long you can stay.

Which Visa Category Are You Really Looking At?

Selecting the right pathway depends on the type of work, the worker's qualifications, and your company's relationship with the worker. Here's how to identify the likely category family.

Is the Work Agricultural and Seasonal?

Choose H-2A when the role is temporary or seasonal agricultural work performed in the United States and the employer can support the required recruitment and DOL certification steps tied to agricultural employment. H-2A has no annual cap, but requires employers to provide housing, transportation, and pay the Adverse Effect Wage Rate.

Is the Work Non-Agricultural but Seasonal or Temporary?

Choose H-2B when the role is temporary non-agricultural work in the United States and the employer can demonstrate a temporary need (such as seasonal, peakload, intermittent, or one-time occurrence) and manage both DOL and USCIS steps on a fixed seasonal timeline. H-2A differs from H-2B in that H-2A is limited to temporary agricultural work while H-2B is limited to temporary non-agricultural work, and both generally require DOL involvement before USCIS petitioning.

Is the Role a Specialty Occupation Requiring a Degree?

Choose H-1B when the job is a specialty occupation requiring at least a bachelor's degree (or equivalent) in a specific field and the employer is prepared for a cap-driven filing cycle and wage/condition obligations. H-1B is subject to an annual lottery for cap-subject positions, with registration typically occurring in March for October start dates.

For UK and EU companies, the big cost difference is lottery risk versus guaranteed processing. H-1B lottery uncertainty forces backup plans. L-1 transfers are predictable if you qualify.

Is the Worker Transferring from a Related Non-U.S. Entity?

Choose L-1A or L-1B when the worker is transferring from a related non-U.S. entity to a U.S. entity and the worker has the required prior employment history with the overseas entity. L-1 is structurally designed for intra-company transfers rather than open-market hires. L-1A is for managers and executives; L-1B is for workers with specialised knowledge.

The key difference: H-1B faces the lottery for new hires with degrees. L-1 skips the lottery but only works for existing employees you're moving between offices.

Does the Worker Have Extraordinary Ability?

Choose O-1 when the candidate can document extraordinary ability or achievement in a qualifying field and the employer needs a non-cap pathway tailored to top-tier profiles rather than standard credential-based eligibility. O-1 requires substantial evidence of sustained national or international acclaim.

Is the Worker a Canadian or Mexican Professional?

Choose TN when the worker is a Canadian or Mexican citizen in a listed professional category under USMCA and the role matches the TN profession requirements. TN is a streamlined professional route that is not structured like H-1B and does not require USCIS petition filing for Canadian citizens at the border.

The Visitor vs. Worker Trap (and How to Avoid It)

Yes. Temporary worker visas (such as H and L classifications) differ from visitor categories (such as B-1/ESTA) in that worker visas authorise employment for the petitioning/sponsoring employer under defined terms, while visitor categories restrict activities and generally do not allow productive employment. A nonimmigrant worker visa is a U.S. immigration status that authorises employment for a specific employer (or sponsor), in a defined role, for a defined period.

The critical distinction is between "business visitor" activities and "productive employment." Business visitors can attend meetings, negotiate contracts, and consult with business associates. They cannot perform work that would generate income from a U.S. source or displace a U.S. worker. Choose "business visitor" travel (such as B-1 or ESTA where eligible) only when the planned U.S. activities are limited to permissible business activities and do not constitute productive employment in the U.S., because using visitor status for work creates avoidable immigration and compliance exposure.

How Long Can You Actually Keep Someone on Each Visa?

"Temporary" ranges from 10 months to 7 years depending on the visa. That changes everything about your budgeting and project planning.

H-1B status allows up to 6 years total, with extensions possible beyond 6 years in certain circumstances (such as pending green card applications). L-1A allows up to 7 years total; L-1B allows up to 5 years total. H-2A and H-2B are tied to the employer's temporary need, typically one year at a time with possible extensions up to 3 years total.

J-1 exchange visitors work on the sponsor's timeline, not yours. Could be 4 months for a summer program or 3 years for a researcher. You can't negotiate it.

Your CFO needs to know: at what point does cycling through temporary visas cost more than going for a green card? Usually around year 3 or 4, the math shifts.

The Mistakes That Get People in Trouble (and How to Stay Out)

The biggest mistake we see? Thinking the visa stamp is all that matters. Wrong. The I-94 they get at the border controls everything. Check it the day they arrive.

Confusing Visa Stamp with Work Authorisation

USCIS petition approval differs from a visa stamp in that an approved petition establishes eligibility for a classification, while the visa stamp is an entry document used at the border and does not by itself define the period of authorised stay. Always verify the I-94 record after entry to confirm the authorised period and classification.

Using Visitor Status for Work Activities

Mid-market companies frequently send employees to the U.S. for "short projects" on ESTA or B-1 visitor status without recognising that productive work requires work authorisation. If the employee is performing duties that would otherwise require hiring a U.S. worker, visitor status is inappropriate regardless of the trip's duration.

Where the Delays Really Happen

For mid-market European/UK employers, Teamed's global mobility playbooks treat "temporary U.S. worker" planning as a 3-agency workflow (DOL to USCIS to State/CBP) with a typical critical-path risk of delay at each handoff rather than at a single "program" gate. Build buffer time into project timelines and have contingency plans for each potential delay point.

Checks You Do at Each Stage So Nothing Slips

Don't assume anything. Check every approval before moving forward.

After DOL: Check those validity dates match your timeline. After USCIS: Make sure the I-797 shows the right visa type and dates. After the consulate: Verify the visa stamp before they fly. After landing: Pull the I-94 online immediately. If CBP gave less time than expected, you need to know now, not at renewal.

When Things Stall: RFEs, 221(g), and Short I-94s

If USCIS issues a Request for Evidence (RFE), respond within the deadline with the specific documentation requested. RFEs are common and don't necessarily indicate denial. If the visa interview is refused under Section 221(g), the consulate needs additional documentation or administrative processing time. Follow up with the specific documents requested.

If the I-94 shows a shorter period than expected, the CBP officer may have limited the stay based on passport validity or other factors. You may need to file an extension before the I-94 expires.

Next Steps: Building Your U.S. Workforce Strategy

The U.S. temporary worker system rewards advance planning. Start pathway identification 6-12 months before the intended start date for cap-subject categories like H-1B. For L-1 and O-1, 3-4 months typically provides adequate buffer.

For companies managing global employment across multiple platforms and employment models, the U.S. temporary worker question is just one piece of a larger workforce strategy puzzle. The decision about which visa pathway to use connects directly to questions about entity establishment, employment model selection, and long-term market commitment.

If you're trying to piece together U.S. immigration advice from three different vendors while managing teams in ten other countries, you know how exhausting that gets. Let's talk through how to handle U.S. complexity as part of your whole global employment picture, not another isolated puzzle.

California Minimum Wage 2026: What Happens When Your LA Hire Costs More Than You Budgeted

You've just approved a hire in Los Angeles. The offer letter says $16.90 per hour, matching California's statewide minimum wage. Then your payroll team flags it: the City of Los Angeles has its own minimum wage, and it's scheduled to reach $18.42 by July 2026. That one wrong rate, repeated across 26 pay periods? You're looking at back wages, penalties that reached $43.7 million in recent California enforcement actions, and an awkward conversation with your new hire.

California's minimum wage hits $16.90 per hour on January 1, 2026. That's the state number. But here's what catches teams off guard: 40 city and county jurisdictions set their own rates above that. When you're already juggling contractors in one system, employees in another, and trying to keep track of who works where, these overlapping wage rules can turn a simple hire into a compliance headache.

The federal minimum wage sits at $7.25 per hour, unchanged since 2009. For California payroll, that number doesn't matter. Your state rate of $16.90 is already more than double the federal floor. The rule is simple: you pay whichever rate is highest. Federal, state, or local. Whatever applies to where the actual work happens, that's your number.

The Numbers You Actually Need for 2026

California's statewide minimum wage is $16.90 per hour effective January 1, 2026 for all employers regardless of size, according to the California Department of Industrial Relations (dir.ca.gov).

The federal minimum wage is $7.25 per hour and has not changed since July 24, 2009, making it irrelevant for California employers who must pay the higher state rate.

California's exempt salary minimum for many white-collar exemptions in 2026 is $70,304 per year, calculated as twice the statewide minimum wage for a 40-hour week.

Fast food employees covered by California's fast food minimum wage framework have a $20.00 per hour minimum wage effective April 1, 2024.

Many California local minimum wages update annually on January 1, making December the critical recertification window for local-rate changes.

The unincorporated areas of Los Angeles County have a minimum wage of $17.81 per hour as of July 1, 2025, exceeding the statewide rate.

What This Guide Can Help You Avoid

After reading this, you'll know how to check the right minimum wage for any California worker without second-guessing yourself. You'll see which rate actually applies when federal, state, and local rules overlap. And you'll have a simple process that holds up when auditors come asking questions. Most teams can set this up in about half an hour for their first employee. After that, it's just a quick check for each new hire.

Before you start: grab your employee work addresses and pull up your payroll system. You'll also want the California DIR website (dir.ca.gov) bookmarked for rate checks. If your team works across multiple California cities, you'll face a choice: track hours by location, or just pay everyone the highest rate that applies. Most teams pick the second option.

Which Minimum Wage Number Do You Actually Pay?

The governing rule is straightforward: when federal and state or local minimum wages differ, the higher applicable wage controls. California's statewide minimum wage of $16.90 per hour always supersedes the federal $7.25 rate. But a local ordinance in San Francisco, Los Angeles, or any of the dozens of other California jurisdictions with their own minimums can supersede the state rate when it's higher.

Picture three levels stacked on top of each other. Federal at the bottom ($7.25), which you can basically ignore in California. State in the middle ($16.90). Local city rates on top, which only apply inside city limits. Your job? Figure out which rates apply to each employee based on where they work, then pay the highest one.

Here's where international companies often slip up: they assume one rate covers all of California. But when your employee drives from San Francisco to Oakland for client meetings, they've crossed into a different minimum wage zone. Same metro area, different rules. That's how underpayment happens.

First: Pin Down Exactly Where They Work

Get the actual address where your employee works. Not their home address if they're remote, but where they sit and do the job. The key question: are they inside city limits with its own wage rules, or in an unincorporated area where only county rules apply?

An incorporated city like Los Angeles, San Francisco, or San Jose has its own municipal government and can enact local minimum wage laws. An unincorporated area falls under county jurisdiction. Los Angeles County, for example, has a minimum wage for unincorporated areas of $17.81 per hour as of July 1, 2025, which differs from the rates in incorporated cities within the county.

Most wage guides give you a nice table of rates but don't tell you how to check if an address is actually inside city limits. This is where teams usually get it wrong. Your county assessor's website typically has an address lookup tool. Type in the address, and it'll tell you if it's in the city or unincorporated county territory.

Lock in the State Rate as Your Floor

Now that you know where they work, confirm the California state rate. The DIR website (dir.ca.gov/dlse/minimum_wage.htm) has the official numbers. For 2026, it's $16.90 per hour. That's your floor. Nobody in California gets paid less than this.

California eliminated the employer-size distinction in previous years, so the rate no longer varies based on whether you have 25 or fewer employees versus 26 or more. Every employer pays the same statewide floor. This simplifies one dimension of compliance while the local ordinance layer adds complexity back in.

Write down $16.90 as your baseline. Every California employee gets at least this much in 2026, no matter where they work. But plenty of them will need more, depending on local rules or special industry rates.

Now Check if the City Has Its Own Rate

Now compare the statewide rate against any applicable local minimum wage. If the employee works in a city or county with its own ordinance, and that local rate exceeds $16.90, the local rate applies.

The DIR keeps a list of local rates, but don't stop there. Go straight to each city's website to confirm. Most cities update their rates on January 1, which means December is when you need to double-check everything before your first payroll run of the new year.

Check if Size Rules Apply to You

Some local ordinances have employer-size thresholds that determine when the local rate applies. A city might require employers with 26 or more employees to pay a higher rate than smaller employers, or the ordinance might apply only to employers with a certain number of employees within city limits.

Pull up the actual city ordinance, not just a summary. The fine print matters here. Some cities count all your employees nationwide to determine if their rate applies to you. Others only count employees working in that specific city. Get this wrong and you could be overpaying or, worse, underpaying.

This is where mid-sized companies often get surprised. You might have 500 employees total but only 5 in San Francisco, putting you below their threshold. Or the opposite. If you're not sure which rate applies, paying the higher one can save you from penalties and back-wage calculations later.

Watch for Special Industry Rates

California has enacted sector-specific minimum wages that apply on top of the geographic hierarchy. Fast food employees covered by California's fast food minimum wage framework have a $20.00 per hour minimum wage effective April 1, 2024. Healthcare workers in covered facilities have minimum wages ranging roughly from $18 to $24 per hour depending on facility type and phase-in schedule.

These industry overlays apply based on the worker's sector and establishment type rather than geography alone. An employee might work in a city with no local minimum wage ordinance but still be entitled to a higher rate because they work in a covered fast food establishment or healthcare facility.

Some industries have their own minimum wage rules on top of everything else. Don't assume based on job titles. Check the actual law to see if your specific type of business or role falls under special rates.

Mark Your Calendar for Rate Changes

California minimum wages change on predictable schedules, typically January 1 for statewide and most local rates. Some local ordinances update on July 1 instead. Industry-specific rates may have their own effective dates and phase-in schedules.

Create a simple calendar with every rate change date for each city where you have employees. Give yourself enough lead time before payroll cutoff to update the system. If you track just three things for each worker, track these: their work address, which city's rules apply, and when the current rate took effect.

When auditors or board members ask how you set wage rates, this documentation gives you a clean answer. You can show exactly how you checked each rate and when you updated it.

When Your Employee Works in Multiple Cities

Employees who work in multiple locations within the same pay period create the trickiest compliance scenario. If someone works three days in San Francisco and two days in Oakland, which rate applies?

You've got two choices here. Option one: track exactly where they work each hour and pay the rate for that specific location. It's cheaper on paper, but only if your time tracking is bulletproof and your payroll system can handle multiple rates in one pay period.

Option two: pay the highest rate that applies anywhere they worked that period. If they spend even one day in San Francisco, they get San Francisco rates for the whole pay period. Yes, it costs more. But it's simpler to manage and you won't get caught underpaying.

In our experience, most companies your size pick option two. The hassle of tracking location-specific hours usually isn't worth the savings. Plus, if you get the rate wrong once, that mistake repeats every pay period until someone catches it. Twenty-six pay periods later, you're looking at a mess.

How Minimum Wage Changes Break Your Exempt Classifications

California's exempt salary minimum for many white-collar exemptions in 2026 is $70,304 per year, calculated as twice the statewide minimum wage multiplied by 2,080 hours. This creates a direct link between minimum wage increases and exempt classification requirements.

Got exempt employees earning right around the threshold? A minimum wage bump can suddenly make them non-exempt. Now they're owed overtime going back to when the rate changed. That's back pay, penalties, and a lot of recalculating.

Every time minimum wage changes, check your exempt employees. Anyone making less than double the new minimum wage for full-time hours needs a raise or needs to start tracking overtime. Make this part of your December checklist along with the rate updates.

What About Those $20 or $25 Minimum Wage Headlines?

The statewide minimum wage is $16.90 for 2026, not $20 or $25. The $20 figure applies specifically to fast food workers under the sector-specific minimum wage framework, not to all California employees. Proposals for higher statewide minimums have circulated, but as of the 2026 rate schedule, $16.90 remains the general floor.

California law allows the minimum wage to be adjusted annually for inflation, which explains why the rate increases incrementally each year. Future increases depend on inflation calculations and any new legislation. For budgeting purposes, assume modest annual increases and verify the official rate each December for the following year.

How to Keep This From Slipping Next January

Put someone's name on this. Usually someone in payroll or HR ops who owns making sure rates are right. Have them check rates at least quarterly, but absolutely in December before the January changes hit.

Keep a simple log: date you updated rates, which cities changed, who approved it, and which payroll run it first hit. Add a "last reviewed" date to your wage documentation. When someone asks, you can show exactly when and how you verified everything.

Go straight to the source: dir.ca.gov for California rates, city websites for local rates. Bookmark them. Blog posts and summaries get outdated fast. The official sites have what you need to stay compliant.

Where Teams Usually Get Caught

The most frequent error is applying the statewide rate when a higher local rate applies. This happens when payroll systems default to state rates and no one verifies local ordinances for each work location. The fix is building jurisdiction verification into your onboarding workflow before the first paycheck.

The second common issue is missing rate change effective dates. An employee hired in November at the correct rate becomes underpaid in January if no one updates the system. Automated payroll systems can help, but someone needs to input the new rates and verify they applied correctly.

Remote workers create a third challenge. If an employee's home address is their work location, the local minimum wage for that address applies. This can create situations where two employees doing identical work for the same company have different minimum wages based solely on where they live.

How California Wage Rules Fit Into Your Bigger Employment Picture

If you're like most mid-market companies with international teams, California minimum wage is just one compliance challenge among many. You've probably got contractors tracked in one system, EOR employees in another, your own entities in a third. Payroll data lives in multiple places.

That fragmentation? It's how wage errors happen. When your employee data lives in three different systems, wage rates end up tracked in spreadsheets and emails. Someone makes an offer based on outdated information. The wrong rate gets locked into payroll, creating unexpected costs. Nobody catches it until it's too late.

Teamed can help mid-market companies bring their scattered employment operations together. We work as your single advisory partner across contractors, EOR, and your own entities. That includes keeping track of wage requirements in every jurisdiction, so California's 40+ different minimum wages don't catch you off guard.

If you're tired of reconciling wage data across multiple systems or getting conflicting advice from different vendors, we can help simplify things. Reach out to our team to discuss how we can support your compliance needs across California and beyond.

Ontario's New Salary and AI Rules: Do They Apply If You Have Fewer Than 25 Employees?

Your recruiter just asked if you need to add salary ranges to job postings. Your CFO wants to know if that new AI disclosure rule affects your ATS. And you're sitting there wondering: do these Ontario rules even apply to us if we're under 25 employees?

The short answer is no. Ontario's ESA amendments on salary disclosure and AI usage disclosure apply only to employers with 25 or more employees on the day a publicly advertised job posting goes live. If you're below that threshold, you're legally exempt from both requirements. That's the rule as it stands for 2026.

But here's what matters more. Even if you're exempt today, posting salary ranges can save you from those awkward compensation calls at the offer stage. And when you hit 26 employees next quarter, you won't be scrambling to update every posting. Let me show you how to figure out where you stand and what to do about it.

What to Check Before You Hit Publish on That Job Posting

Ontario's salary disclosure requirement applies only to employers with 25 or more employees on the day a publicly advertised job posting is published.

The AI usage disclosure requirement under Bill 149 uses the same 25-employee threshold as the salary disclosure rules.

Employee count typically includes all individuals on payroll at the snapshot date, including part-time and fixed-term workers, unless the statute specifies otherwise.

If you're hovering between 20 and 30 employees, check your headcount before every posting. You could be at 24 on Monday when you draft the job ad and 26 by Friday when it goes live. Keep a simple spreadsheet with your count on posting day.

Getting AI disclosure right doesn't need to be complicated. You can set up the basics in an afternoon: write a one-paragraph notice for candidates, list which tools in your hiring process use automation, and give your recruiter a simple checklist to follow.

For salary range postings, a common internal variance limit is to keep actual offers within the posted range at least 80% of the time and document exceptions to reduce perceived misrepresentation risk, according to Teamed's compensation governance guidance.

Here's What You'll Know in 30 Minutes

You'll know if these rules apply to you today. You'll have a simple way to count employees that holds up if anyone asks. And you'll walk away with a clear plan, whether that's updating your postings now or just keeping an eye on your headcount.

Time required: 30-45 minutes to complete the full assessment.

Prerequisites: Access to your current payroll records, knowledge of your hiring tools and processes, and clarity on your corporate structure (single entity vs. multi-entity group).

First, Count Heads on the Day You Post

The threshold question hinges on one specific moment: how many employees do you have on the day you publish a publicly advertised job posting? Not your average headcount. Not your FTE count. The actual number of people on your payroll on that specific date.

Ontario's ESA amendments use a "number of employees" approach rather than a full-time equivalent calculation. This means part-time workers count as whole persons. A company with 15 full-time employees and 10 part-time employees has 25 employees for threshold purposes, even if the part-time workers collectively represent only 3 FTEs.

Expected result: A clear count of all employees on your payroll, including full-time, part-time, and fixed-term workers.

What Counts Toward Your Employee Total?

Include in your count: permanent full-time employees, permanent part-time employees, fixed-term contract employees, and employees on leave (maternity, disability, or other statutory leaves). These individuals remain employees during their leave period.

The treatment of temporary agency workers and independent contractors requires more careful analysis. Independent contractors are not employees and don't count toward your threshold. Temporary agency workers are typically employees of the agency, not your organisation, so they generally don't count toward your threshold either.

If you're uncertain about any worker's classification, that's a separate compliance question worth addressing. Misclassification risk is real, and getting it wrong affects more than just your threshold calculation.

Step 2: Assess Your Corporate Structure

A multi-entity group structure differs from a single legal employer in threshold analysis because some rules apply per legal entity while others aggregate affiliated employers under common control. For Ontario's ESA amendments, the threshold applies at the employer level.

If you operate multiple legal entities in Ontario, each entity is assessed separately. A parent company with 30 employees and a subsidiary with 15 employees would have different compliance obligations. The parent company must comply; the subsidiary is exempt.

However, if your corporate structure involves common ownership or control, consult with legal counsel to confirm how the threshold applies to your specific situation. Some jurisdictions aggregate affiliated employers, and while Ontario's current rules focus on the individual employer, this is an area where regulatory interpretation can evolve.

Expected result: Clarity on which legal entity or entities you're assessing and whether any aggregation rules apply.

How Do You Count Employees if Your Headcount Fluctuates?

This is where many small employers get tripped up. Your headcount isn't static. Seasonal hiring, project-based work, and normal turnover mean you might be at 23 employees one month and 27 the next.

The rule is straightforward but requires discipline: you assess your employee count on the day each publicly advertised job posting is published. If you post a job on March 15 and have 24 employees that day, you're exempt for that posting. If you post another job on April 1 and have 26 employees, you must comply for that posting.

Treat an "under 25 employees" question as "Depends" when your headcount fluctuates across the 25 line due to seasonal hiring, fixed-term peaks, or recent acquisitions. In these situations, you need a system for checking headcount before each posting goes live.

If your hiring plan shows you'll cross 25 employees this year, start preparing now. Once you hit that 25th person, your very next posting needs the salary range and AI notice. No grace period. Set up your templates before you need them, and consider your broader compliance readiness as you scale.

Which Bucket Are You In?

Based on your employee count and corporate structure assessment, you'll fall into one of three categories.

Applies (25+ employees): You must include salary ranges in all publicly advertised job postings and disclose AI usage in your hiring process. Move to the compliance implementation section below.

Doesn't apply (under 25 employees, stable): You're legally exempt from both requirements. Consider voluntary compliance for the strategic benefits outlined in the best practices section.

Partially applies (fluctuating around threshold): You need a per-posting assessment process. Some postings will require compliance; others won't. This is the most operationally complex scenario.

What Does Salary Disclosure Require in Practice?

For employers who meet the 25-employee threshold, Ontario's rules require including expected compensation information in publicly advertised job postings. This means stating a salary range or, where applicable, an hourly wage range.

A job posting pay transparency rule is a legal requirement that an employer include a salary or wage range in an external job advertisement so candidates can assess compensation before applying. The range should reflect what you genuinely expect to pay, not an artificially wide band designed to avoid meaningful disclosure.

What to include: The expected hourly or salary range for the position. If the role includes variable compensation (commissions, bonuses), you can note that additional compensation is available beyond the base range.

What to avoid: Ranges so wide they're meaningless (£30,000-£100,000), ranges that don't reflect actual offers, or omitting the range entirely with vague language like "competitive compensation."

When a pay range is expressed in base salary only, employers commonly add a one-line qualifier that variable compensation and benefits are additional. This avoids candidates interpreting the range as total compensation.

What Does AI Usage Disclosure Require?

An AI-in-hiring disclosure rule is a legal requirement that an employer tell job applicants when automated tools or artificial intelligence are used to screen, assess, or rank candidates as part of a hiring process. Ontario's Bill 149 requires this disclosure for employers meeting the 25-employee threshold.

The disclosure must appear in the job posting itself. Candidates should know before they apply whether AI will be involved in evaluating their application, especially since only 26% trust AI to evaluate them fairly.

What counts as AI usage? Automated resume screening, AI-powered candidate ranking or scoring, chatbots that assess candidate responses, and video interview platforms that analyse speech patterns or facial expressions. If a tool makes decisions or recommendations about candidates without human review of each individual, it likely triggers disclosure.

What typically doesn't count? Scheduling tools, applicant tracking systems used purely for organisation, and communication platforms. The distinction is between tools that automate decisions versus tools that automate administration.

In multi-country hiring, a typical mid-market company uses 3 to 7 distinct recruitment tools across sourcing, ATS, assessments, scheduling, and background checks, according to Teamed's HR tech rationalisation framework. This increases the likelihood that at least one tool includes automated screening or scoring features. You need to know what your tools actually do.

Make a List of Every Tool That Touches Candidates

Even if you're under 25 employees and exempt from disclosure requirements, knowing what AI tools you use in hiring is essential for future compliance and risk management.

An AI tool inventory is an internal register listing each hiring-related technology that performs screening, scoring, ranking, or automated decision support. Include the vendor name, purpose, data inputs, and where in the recruitment funnel it's used.

How to build it: List every tool in your hiring process. For each tool, answer: Does it screen, score, rank, or make recommendations about candidates? If yes, it belongs on your AI inventory.

Escalate to legal review when the hiring process includes automated rejection or automated ranking of applicants. Fully automated decision-making triggers higher regulatory sensitivity than assistive tools.

Time to Fix Those Job Posting Templates

If you meet the threshold, or if you're implementing voluntary compliance, you need to update your job posting templates. A small employer can usually standardise pay transparency and AI disclosure across all requisitions in 60 to 90 minutes by updating one job-post template, one application form footer, and one recruiter email template, based on Teamed's implementation checklists for resource-constrained HR teams.

Sample salary disclosure language: "The expected salary range for this position is £55,000-£70,000 annually, based on experience and qualifications. Additional variable compensation may be available based on performance."

Sample AI disclosure language: "We use automated tools to assist in reviewing applications for this position. These tools help us screen resumes and assess candidate qualifications. All final hiring decisions are made by our team."

If you're hiring in multiple places, use one master template. Otherwise, you'll wake up to find your Toronto manager posted a job without the salary range while you were updating the Ottawa version. Lock down who can edit the master, and make everyone use it.

If You're Under 25, Here's What I'd Still Do

Here's where the practical guidance diverges from the legal minimum. Even if Ontario's rules don't apply to you, voluntary compliance makes strategic sense.

Candidate trust: Job seekers increasingly expect salary transparency. 72% of candidates are more likely to apply when salary is included, and postings without ranges attract candidates who may have misaligned expectations.

Preparation for growth: If your 12-month hiring plan shows you approaching 25 employees, building compliant processes now avoids scrambling later. The obligations become effective immediately when you cross the threshold.

Competitive positioning: In tight labour markets, transparency differentiates you from employers who hide compensation information. Candidates notice.

Reduced disputes: Clear salary ranges reduce the likelihood of offer-stage negotiations that fall apart due to misaligned expectations. You waste less time on candidates who would never accept your actual compensation.

Choose a "minimum compliance plus voluntary best practice" approach when the rule doesn't apply under 25 employees. Publishing pay ranges and AI usage notices still reduces candidate disputes and prepares you for growth past the threshold.

Before You Post Another Job

After implementing your compliance approach, verify it's working correctly.

For salary disclosure: Review your live job postings to confirm ranges appear correctly. Check that ranges reflect actual compensation expectations. Monitor whether offers fall within posted ranges at least 80% of the time.

For AI disclosure: Confirm disclosure language appears in all postings where AI tools are used. Verify your AI tool inventory is current and complete. Test that candidates see the disclosure before submitting applications.

For threshold monitoring: Establish a monthly headcount review process. Document your employee count on the date of each job posting. Create alerts when headcount approaches 25.

A reasonable internal control for audit readiness is to retain the job posting version and candidate disclosure text for at least 3 years after the posting is removed from public access, as required by Ontario's regulations, because most hiring disputes and regulator questions arise after a hiring decision is made.

Troubleshooting Common Issues

"Our headcount changes constantly." Implement a pre-posting checklist that includes headcount verification. Assign responsibility for checking the number before any job goes live.

"We don't know if our tools use AI." Contact your vendors directly. Ask specifically: "Does this tool use automated screening, scoring, ranking, or decision-making for candidates?" Document their responses.

"Our salary ranges are confidential." This is a policy choice, not a legal constraint. If you meet the threshold, the law requires disclosure regardless of internal confidentiality preferences. If you're under 25, you can maintain confidentiality, but consider whether it's serving your hiring goals.

"We operate in multiple provinces/countries." Ontario's rules apply to jobs in Ontario. Other jurisdictions have their own requirements. Delaware, for example, requires salary disclosure for employers with 25+ employees effective September 2027. Build jurisdiction-specific compliance into your posting process.

If You're Close to 25, Do This Next

For companies approaching or exceeding the 25-employee threshold, the immediate priority is implementing compliant job posting templates and building your AI tool inventory. These are one-time setup tasks that then require only periodic maintenance.

For companies well under 25 employees, the priority is deciding whether voluntary compliance serves your hiring goals and establishing a monitoring system for when your headcount approaches the threshold.

If you're hiring in multiple countries, this gets messy fast. Ontario wants salary ranges. The EU's requiring them by June 2026. California already does. Instead of updating templates country by country as laws change, build one approach that works everywhere. You'll thank yourself later.

If you're managing hiring across multiple countries with different transparency requirements, fragmented compliance approaches create risk. A practical compliance cadence for fast-moving pay transparency changes is a quarterly review of job-post templates and hiring workflows, because most mid-market hiring teams reuse templates for 90+ days at a time, according to Teamed's operating model for unified global employment operations.

Growing Past 25? Here's How to Stay Ready

Ontario's ESA updates represent a broader trend toward hiring transparency. Whether you're at 15 employees or 50, building transparent hiring practices now positions you well for regulatory changes and candidate expectations.

At 24 employees, these rules don't apply. At 25, they do. Simple as that. But here's what I've seen work: companies that post salary ranges before they have to waste less time on compensation mismatches. Candidates self-select better. Your recruiters stop having those painful "actually, our budget is..." conversations.

When you're posting the same role in Toronto and Berlin, different rules apply. Different thresholds. Different disclosure requirements. If you're tired of checking three different compliance guides every time you post a job, we can help you build one approach that works across all your markets. No more last-minute scrambles when laws change.

Employer of Record USA and Canada 2026: When Your Board Wants North American Coverage Yesterday

Your CFO just approved headcount for both the US and Canada. The job descriptions are ready, candidates are in pipeline, and someone in HR is now staring at a spreadsheet trying to figure out how to make one hiring plan work across two countries with different payroll systems, tax structures, and benefits expectations.

Teamed is the unified global employment partner for mid-market companies managing international teams across multiple platforms, vendors, and employment models. We've guided over 1,000 companies through exactly this scenario, and the pattern is consistent: teams that treat US and Canada as "basically the same" run into payroll failures, benefits gaps, and compliance surprises within the first 90 days.

By the end of this guide, you'll know exactly where US and Canada hiring breaks down, which vendors can actually handle both markets, and how to get first payroll right without the usual chaos.

What Actually Slows Down First Payroll in the US and Canada

If you want first pay to land on time in both countries, budget at least two to three weeks once you've handed over clean employee data. That's based on what we've seen across hundreds of implementations.

US payroll processing cutoffs are often 2-5 business days before pay date, and missing the cutoff typically pushes payment to the next cycle even if onboarding is otherwise complete.

Canadian direct deposit prenote or banking validation commonly takes 3-5 business days when a new employee bank account is added, which is a frequent cause of first-payroll exceptions if started late.

A dual-country EOR rollout usually requires collecting 20-35 unique data fields per hire before payroll can be configured without manual rework.

A practical vendor shortlist for US and Canada EOR selection is usually 3-5 providers because each additional provider adds security review, legal redlining, and parallel payroll validation work that typically extends timelines by 1-2 weeks.

What Is an Employer of Record and When Does It Make Sense for US and Canada Hiring?

An Employer of Record (EOR) is a third-party organisation that becomes the legal employer of a worker in a specific country, running local payroll, statutory tax filings, and employment administration while the client controls day-to-day work. The EOR handles payroll, taxes, and compliance with local employment law, while your team still reports to you and works on your projects.

For companies hiring in both the US and Canada without established entities in either country, an EOR typically makes sense when you need to hire in under 30 days, when you're testing market demand before committing to entity formation, or when you have fewer than 10 employees planned per country over the next 12 months.

The alternative is establishing your own legal entity in each country. Choose a local entity when you expect sustained hiring of 10+ employees in either the US or Canada within 12 months and you need direct control over benefits plan design, signatory authority, and local policies. Entity establishment in both the US and Canada typically takes 2-4 months and requires ongoing compliance infrastructure.

A third option exists for the US specifically: a Professional Employer Organisation (PEO). Choose a PEO in the US when you already have a US entity and want co-employment access to broader group benefits and HR administration while retaining primary employer status. An EOR differs from a PEO in risk allocation because an EOR is the legal employer of the worker in-country, while a PEO typically relies on the client's local entity and a co-employment structure.

What Are the Key Operational Differences Between US and Canada Employment?

The assumption that US and Canada employment works similarly because both are North American markets causes more first-payroll failures than any other misconception. Here's what actually differs.

Payroll and Tax Administration

US payroll is materially state- and sometimes city-specific. An employee in California faces different withholding requirements than an employee in Texas, and New York City adds local income tax of 3.078% to 3.876% on top of state requirements. Your EOR must support state-level tax registration and remittance for every state where you have employees.

Canadian payroll is primarily federal plus province-based with fewer local withholding layers. The Canada Pension Plan (CPP) and Employment Insurance (EI) deductions apply nationally, with provincial income tax calculated based on the employee's province of residence. Quebec operates its own pension plan (QPP) with a 6.30% contribution rate versus 5.95% for CPP, and requires separate registration.

Running US and Canadian payroll together differs from running either alone because each country uses distinct statutory deductions, remittance schedules, and year-end reporting formats. A provider must support two parallel compliance calendars without forcing one country's workflow onto the other.

Benefits Expectations

US employment administration differs from Canadian employment administration in benefits expectations because US hires often expect employer-sponsored medical coverage as a primary hiring criterion, with 87% of full-time private-industry workers having access to medical care benefits. In the US, health insurance is frequently the deciding factor in whether a candidate accepts an offer.

Canadian hires typically treat supplemental health and dental plans as the key add-on to public healthcare, with 66.8% of employees having workplace medical or dental benefits. The provincial healthcare systems cover most medical expenses, so employer-sponsored benefits focus on prescription drugs, dental, vision, and extended health services.

A US and Canada EOR rollout that includes benefits enrollment typically needs at least 7-10 calendar days of lead time before the intended coverage start date because carrier rules and eligibility windows can delay effective dates beyond the hire date.

Termination and Notice Requirements

US termination compliance in most states follows at-will employment principles, meaning employers can terminate without cause in most circumstances. However, California and New York have significantly more complex requirements including final-pay timing rules and extensive leave entitlements.

Canadian termination compliance requires careful handling of notice or pay-in-lieu concepts at the province level. Ontario, for example, requires written notice or pay-in-lieu based on length of service, and common law notice periods can exceed statutory minimums significantly.

US vs Canada EOR Requirements: Side-by-Side Comparison

How to Pick an EOR Without Getting Sold To

First, Know What You Actually Need

Start by documenting what you actually need, not what vendors want to sell you. Map your hiring timeline, expected headcount by country, benefits requirements, and integration needs with existing HR systems.

For US and Canada specifically, clarify whether you need the same provider for both countries or whether country-specialist providers make more sense. Choose a single EOR vendor for both the US and Canada when you require unified reporting, one invoice cadence, consistent onboarding workflows, and one support escalation path across both countries.

Choose separate country-specialist providers when benefits competitiveness is a priority and you need deeper carrier choice, region-specific HR advisory, or province/state-specific policy support that a generalist may not offer.

Step 2: Build Your Shortlist

A practical vendor shortlist for US and Canada EOR selection is usually 3-5 providers. Each additional provider adds security review, legal redlining, and parallel payroll validation work that extends timelines.

EOR selection projects in mid-market companies commonly involve 3 core stakeholders (HR, Finance, and Legal/Compliance) and 6-12 total approvers or contributors once security, IT, and procurement are included.

Step 3: Validate Compliance and Benefits Capabilities

Ask specific questions about state-level US compliance. Can the provider support employees in California with its meal and rest break requirements? What about New York's final pay on termination day rules?

For Canada, verify Quebec capabilities separately. The QPP, QPIP, and French-language documentation requirements mean Quebec operations require distinct compliance infrastructure.

On benefits, understand exactly what plans are available and how enrolment timing works. Generic statements about "competitive benefits" don't tell you whether the medical plan will meet candidate expectations in your target markets.

Step 4: Run a Pilot Hire

Before committing to a full rollout, run a pilot hire in each country. This surfaces integration issues, payroll timing problems, and support responsiveness before they affect your entire workforce.

The pilot should include a complete payroll cycle with all deductions, benefits enrollment with actual coverage verification, and at least one support escalation to test response times.

Step 5: Scale the Rollout

Once the pilot validates the provider's capabilities, scale to your full hiring plan. Maintain the same data collection discipline and payroll cutoff awareness that made the pilot successful.

What Should You Include in an EOR Evaluation Scorecard?

Red flags to watch for include opaque fee structures where you can't see line-item costs, limited benefits options that won't meet candidate expectations, and support models that route you to chatbots or offshore queues for complex questions.

Your First 90 Days: What Has to Happen When

Days 1-30: Foundation

HR responsibilities: Finalise job descriptions and compensation structures for both countries. Collect employee data including identity documents, tax residency indicators, bank details, and emergency contacts. A dual-country EOR rollout usually requires collecting 20-35 unique data fields per hire.

Finance responsibilities: Confirm budget allocation by country. Establish invoice processing workflows. Verify currency handling for CAD and USD payments.

Legal/Compliance responsibilities: Review employment contracts for both jurisdictions. Confirm worker classification rationale. Document right-to-work verification requirements.

Expected outcome: Complete data handoff to EOR provider with all required fields populated.

Days 31-60: First Payroll Readiness

HR responsibilities: Complete benefits enrolment with adequate lead time. Verify onboarding documentation is signed and filed. Confirm work location accuracy for tax purposes.

Finance responsibilities: Validate payroll preview reports before processing. Confirm banking details are verified in both countries. Establish gross-to-net reconciliation process.

Legal/Compliance responsibilities: Verify employment contracts are compliant with provincial/state requirements. Confirm I-9 completion for US employees. Document SIN collection for Canadian employees.

Expected outcome: First payroll runs accurately in both countries with no payment delays.

Days 61-90: Making It Boring (In a Good Way)

HR responsibilities: Conduct employee experience check-ins. Document any onboarding friction points. Establish ongoing support escalation procedures.

Finance responsibilities: Complete first payroll reconciliation. Verify all statutory remittances were filed correctly. Establish ongoing reporting cadence.

Legal/Compliance responsibilities: Audit employment documentation for completeness. Verify benefits coverage is active as expected. Document any compliance gaps for remediation.

Expected outcome: Stable ongoing operations with documented processes for future hires.

What Are the Most Common First-Payroll Failures and How Do You Prevent Them?

Late cutoff submission: US payroll processing cutoffs are often 2-5 business days before pay date. Missing the cutoff pushes payment to the next cycle. Prevention: Build cutoff dates into your project timeline with 2-day buffer.

Banking validation delays: Canadian direct deposit prenote commonly takes 3-5 business days. Starting this process late causes payment failures. Prevention: Collect bank details during offer acceptance, not after start date.

Missing tax forms: US employees need W-4 completion. Canadian employees need TD1 forms for both federal and provincial withholding. Prevention: Include tax form completion in pre-boarding checklist.

Incorrect work location: State and provincial tax withholding depends on where the employee actually works, not where the company is headquartered. Prevention: Verify physical work location during onboarding.

Benefits deduction timing: Coverage effective dates and payroll deduction start dates don't always align. Prevention: Confirm benefits enrolment timing with carrier rules before communicating coverage dates to employees.

When Should You Consider Moving from EOR to Your Own Entity?

Teamed's graduation model provides a framework for this decision. The transition from EOR to owned entity typically makes economic sense when you reach 10+ employees in either the US or Canada, when you're planning a 3+ year presence in the market with stable or growing headcount, and when your annual EOR costs exceed what entity setup plus ongoing administration would cost.

Both the US and Canada are classified as Tier 1 (low complexity) jurisdictions in Teamed's Country Concentration Framework, meaning the entity threshold is 10+ employees for native English operations. The common law systems, English operating language, and predictable regulatory frameworks in both countries make entity establishment relatively straightforward compared to higher-complexity markets.

The graduation model advantage is continuity. Working with a single advisory relationship that supports you from EOR through entity transition eliminates the disruption of switching providers and re-onboarding employees when your employment model evolves.

Making the Decision

Hiring across the US and Canada with a single EOR strategy is entirely achievable, but it requires understanding the operational differences between the two systems and planning for them explicitly. The companies that struggle are the ones that assume similarity and discover the differences during their first payroll run.

The companies that succeed build their implementation timeline around the actual requirements: 10-15 business days minimum from data handoff to pay-date readiness, separate attention to state-level US compliance and provincial Canadian requirements, and realistic expectations about benefits enrollment timing.

If you're evaluating EOR providers for US and Canada hiring and want to validate your approach before committing, talk to the experts at Teamed. We can review your specific situation and help you build an implementation plan that accounts for the operational realities of both markets.

U.S. Tax Obligations When Your European Company Sends Workers to America

Last month, a UK fintech's CFO called us in a panic. Their lead developer had been working from their New York office for four months, and suddenly their payroll provider was asking about U.S. tax withholding. Nobody had tracked the days. Nobody knew who owned what. The scramble to fix it cost them weeks and thousands in penalties.

The answer depends almost entirely on one thing most HR leaders don't fully understand until it's too late: U.S. tax residency status. The IRS doesn't care about your passport or visa type. It cares about whether you're a "resident alien" or "nonresident alien" for tax purposes, and that single classification determines whether the U.S. taxes your worldwide income or just your U.S.-source earnings.

Teamed is the unified global employment partner for mid-market companies managing international teams across multiple platforms, vendors, and employment models. We've seen European companies stumble into unexpected U.S. tax obligations because nobody mapped the residency rules to their actual workforce movements. This guide gives you the decision framework to avoid that.

The Numbers HR and Finance Teams Actually Need

If you're paying dividends, royalties, or interest to a nonresident, the starting withholding rate is 30% unless you have treaty paperwork on file that says otherwise.

The IRS counts days using a three-year weighted formula: all current year days, plus one-third of last year's days, plus one-sixth of the year before that. Hit 183 total, and you're a U.S. tax resident. This is the calculation HR should run before any assignment extension.

A person must be physically present in the U.S. for at least 31 days in the current year to potentially meet the substantial presence test.

U.S. federal payroll taxes for employees include Social Security tax of 6.2% and Medicare tax of 1.45% withheld from wages, with matching employer contributions at the same rates.

Nonresidents file Form 1040-NR for U.S.-source income only. Residents file Form 1040 for worldwide income.

If your finance team is paying a non-U.S. person, you'll need a W-8BEN (individuals) or W-8BEN-E (entities) to justify any treaty rate reduction. Without it, you withhold at 30%.

What the IRS Actually Cares About (And What It Doesn't)

A foreigner for U.S. tax purposes is an individual who is not a U.S. citizen and is classified by the IRS as either a resident alien or a nonresident alien for federal income tax rules. This classification has nothing to do with immigration status, visa type, or where your employer is headquartered.

The distinction matters because it determines the scope of U.S. taxation. Resident aliens are generally taxed on worldwide income, just like U.S. citizens. Nonresident aliens are generally taxed only on U.S.-source income and certain income effectively connected with a U.S. trade or business.

Here's where European HR teams often get tripped up: many visa holders become resident aliens under the substantial presence test without realising it. A UK employee on a short-term U.S. assignment can accidentally trigger U.S. tax residency through accumulated days, creating unexpected withholding obligations for the employer.

Two Tests That Decide Whether You're in U.S. Payroll Territory

The IRS uses two primary tests to determine whether a non-citizen is a resident alien: the green card test and the substantial presence test. Meeting either one makes you a U.S. tax resident.

The Green Card Test

The green card test is straightforward. A person is a U.S. tax resident for any calendar year in which they are a lawful permanent resident (green card holder) at any time, unless a treaty position is properly claimed and documented. This applies regardless of how many days they actually spend in the U.S.

The Substantial Presence Test

The substantial presence test catches more people than most expect. You meet this test if you're physically present in the U.S. for at least 31 days during the current year AND at least 183 days using a weighted three-year formula.

The formula works like this: count all days present in the current year, plus one-third of the days present in the prior year, plus one-sixth of the days present in the second prior year. If that total reaches 183, you've met the test.

Consider a German project manager who spent 120 days in the U.S. in 2025, 90 days in 2024, and 60 days in 2023. The calculation: 120 + (90 × 1/3) + (60 × 1/6) = 120 + 30 + 10 = 160 days. Not a resident. But add another 25 days in 2025, and suddenly they've crossed the threshold.

Teamed highlights this as the most common "unexpected tax residency" trigger for short-term U.S. assignments from Europe. The 31-day minimum in the current year is a practical trip-planning control that HR teams should monitor.

What Taxes Do Nonresident Aliens Pay in the USA?

Nonresident aliens face a different tax regime than residents. They're generally taxed only on U.S.-source income, but the rules for how that income is taxed vary significantly by income type.

Federal Income Tax on U.S.-Source Income

Nonresidents deal with two income buckets: wages and business income from U.S. work (called ECI), and passive payments like dividends, interest, and royalties (called FDAP).

Effectively connected income is income connected with the conduct of a U.S. trade or business. This includes wages for work performed in the U.S., even if paid by a foreign employer. ECI is taxed at graduated federal income tax rates (10% to 37% in 2026), and the nonresident can claim deductions against this income.

FDAP income (fixed, determinable, annual, or periodical income) includes U.S. dividends, certain interest, rents, royalties, and similar passive payments. FDAP is typically subject to a flat 30% withholding tax on the gross amount, with no deductions allowed. Tax treaties can reduce this rate significantly.

When Do Nonresidents Owe State Taxes?

Here's what catches European employers: states don't care about federal residency tests. They look at where the work happens. Work in California for a week? California wants its cut, regardless of your federal status.

California and New York are particularly aggressive. A nonresident who works even a few days in these states may trigger filing requirements and withholding obligations. California requires 7% withholding on California-source payments to nonresidents exceeding $1,500 annually.

For European companies, state tax creates a practical problem: you need state withholding registration, payroll infrastructure, and W-2 capability. Without a U.S. entity, that often means working through a U.S. payroll provider or EOR to handle the compliance properly.

What Taxes Do Resident Aliens Pay in the USA?

Resident aliens face the same tax obligations as U.S. citizens. This means worldwide income reporting on Form 1040, including income earned outside the U.S.

Federal Income Tax on Worldwide Income

Resident aliens report all income from all sources, whether earned in the U.S., the UK, Germany, or anywhere else. Federal income tax rates for 2026 range from 10% to 37%, depending on taxable income and filing status.

The good news: resident aliens can claim the Foreign Earned Income Exclusion (up to $132,900 in 2026) if they meet certain requirements, and they can use the Foreign Tax Credit to offset U.S. taxes with taxes paid to other countries. This prevents true double taxation in most cases.

Payroll Taxes (FICA)

Both resident and nonresident aliens working as employees in the U.S. generally owe payroll taxes. Social Security tax is 6.2% of wages up to the annual wage base ($184,500 for 2026). Medicare tax is 1.45% on all wages, with an additional 0.9% on wages exceeding $200,000.

Some nonresident aliens are exempt from FICA under specific visa categories (F-1 students, J-1 scholars for limited periods) or under totalization agreements between the U.S. and their home country. The UK, Germany, France, and most EU countries have such agreements.

How Does U.S. Tax Treatment Vary by Income Type?

The practical reality for most foreigners is that U.S. tax outcomes are driven by withholding at payment time, not by year-end tax computation. Understanding which income types trigger which withholding rules is essential for HR and Finance teams managing cross-border payments.

For U.S. federal self-employment tax, the combined Social Security and Medicare rate is 15.3% (12.4% Social Security + 2.9% Medicare) on net self-employment income. Teamed uses this figure when comparing U.S. employee versus contractor cost models for European companies expanding into the U.S.

What's the Difference Between Tax Withheld and Tax Owed?

Federal income tax differs from withholding tax because federal income tax is the final liability computed on a tax return, while withholding tax is a prepayment mechanism collected at the time of payment that can exceed or fall short of the final tax owed.

This distinction creates reconciliation problems for HR and Finance teams. A nonresident alien who had 30% withheld on U.S. dividends may owe less (if a treaty applies) or may have other income that wasn't subject to withholding. Either way, they typically must file a U.S. tax return to reconcile.

Nonresident aliens file Form 1040-NR. Resident aliens file Form 1040. The filing deadline is generally April 15 for residents and June 15 for nonresidents (with extensions available).

Which Forms Control U.S. Tax Withholding for Foreigners?

The document that controls withholding is often more important than the tax return filed months later. Getting this wrong creates immediate compliance exposure.

W-8BEN and W-8BEN-E

Form W-8BEN (for individuals) and W-8BEN-E (for entities) document foreign status and claim treaty benefits. Payers use these forms to determine whether to withhold at 30% or a reduced treaty rate. Without a valid W-8, payers must withhold at the full 30% rate.

These forms are critical for FDAP payments: dividends, royalties, certain interest, and similar passive income. They're also used for independent contractor payments to foreign persons.

W-9

Form W-9 is for U.S. persons, including resident aliens. If someone provides a W-9, the payer treats them as a U.S. person for withholding purposes. This means no automatic 30% withholding, but it also means the person is certifying U.S. tax status.

W-2 and 1099

Form W-2 reports wages paid to employees. Form 1099 (various types) reports payments to non-employees. Both are information returns that help the IRS match reported income to tax returns.

How Do Tax Treaties Affect What Foreigners Pay?

Tax treaties between the U.S. and other countries can significantly change tax outcomes, but they don't change everything. Understanding what treaties typically modify, and what they don't, prevents costly assumptions.

What Treaties Usually Change

Treaties commonly reduce FDAP withholding rates. The U.S.-UK treaty, for example, reduces dividend withholding from 30% to 15% (or 0% for certain pension funds). The U.S.-Germany treaty has similar provisions.

Treaties also provide exemptions for certain categories: students, trainees, teachers, and researchers may be exempt from U.S. tax on specific income types for limited periods. And treaties provide "tie-breaker" rules when someone might be considered a tax resident of both countries.

What Treaties Usually Don't Change

Treaties don't eliminate the need for documentation. You still need valid W-8 forms to claim treaty benefits. Treaties don't override state tax obligations, which operate independently. And treaties don't change payroll tax requirements unless a totalisation agreement specifically addresses social security.

Pull in tax counsel when someone's claiming treaty benefits for: reduced dividend or royalty withholding, student or trainee exemptions, residency tie-breakers, or the short-term business visitor exemption. These situations need careful documentation to hold up under scrutiny.

Common Scenarios: Which Taxes Apply?

F-1 Student Working Part-Time

F-1 students are generally exempt from the substantial presence test for five calendar years. During this period, they're nonresident aliens with specific IRS classification rules taxed only on U.S.-source income. They're also exempt from FICA on wages paid for on-campus employment or employment authorised under their visa.

H-1B Worker

H-1B workers are not exempt from the substantial presence test. Most H-1B holders become resident aliens within their first or second year in the U.S. and are then taxed on worldwide income. They owe FICA like any other employee.

Short-Term Business Visitor

A UK executive visiting the U.S. for a two-week client meeting generally remains a nonresident alien. If they receive no U.S.-source wages (their salary continues from the UK employer for UK-based duties), they may have no U.S. tax obligation. But if they're paid specifically for U.S. work, that income is U.S-source ECI.

Foreign Investor with U.S. Rental Property

Rental income from U.S. real property is U.S-source income. Nonresident aliens can either accept 30% gross withholding or elect to treat the rental income as ECI, allowing deductions and graduated rates. Most choose the net election because it typically results in lower tax.

What Should European Employers Do About U.S. Tax Compliance?

Most search results explain IRS residency tests and filing forms but don't provide a CFO-ready map linking residency status, income category, default withholding rate, and the specific document that controls withholding in a single decision flow. That's the gap that creates compliance failures.

Your U.S. tax checklist: Track cumulative U.S. days for each worker (HR owns this). Determine state payroll registration needs based on work location (Finance/Legal owns this). Coordinate UK/EU payroll with U.S. withholding to avoid gaps (Payroll owns this). Collect W-8 forms before any payments (Finance owns this).

Don't stop UK PAYE just because someone's working in the U.S. You'll often run both countries' withholding simultaneously, at least until you sort out the tax treaty position and residence status.

Getting U.S. Tax Compliance Right

The complexity of U.S. taxes for foreigners isn't the rules themselves. It's the interaction between residency status, income type, withholding requirements, treaty positions, and state obligations. Getting any one of these wrong creates exposure for both the individual and the employer.

Mid-market companies managing international teams across multiple countries face this challenge constantly. Contractors in one system, EOR employees in another, owned entities somewhere else, and tax compliance scattered across all of them. The operational reality is that U.S. tax outcomes for nonresidents are often driven by gross withholding at payment time rather than by year-end tax computation, which is the key reconciliation problem HR and Finance teams face when paying non-U.S. workers or vendors.

If you're making decisions about U.S. employment structures without a clear map of the tax implications, you're taking on risk you don't need to carry. Talk to the experts at Teamed to see how unified global employment operations can give you visibility and control across your entire international workforce.

When Your Contractor Is Really an Employee: A Guide to US Conversion

Your finance team just flagged a contractor who's been with you for eighteen months. She uses a company laptop, attends your weekly standups, and reports to your engineering manager. The question isn't whether she's doing good work. The question is whether she's actually an employee under US law and what happens next.

Contractor conversion in the USA means changing a worker from 1099 independent contractor to W-2 employee. It's a complete shift: you'll withhold taxes, provide benefits, apply company policies, and take on employer obligations. For mid-market companies juggling contractors here, EOR employees there, and entities somewhere else, a botched conversion can trigger audits, back taxes, and penalties that ripple through every country where you operate.

We'll show you what contractor conversion actually involves, why companies pull the trigger, and how to handle the transition so you're not scrambling when the auditor calls. You'll know what documents to prepare, which decisions need legal input, and what breaks if you get the timing wrong.

What Usually Changes First

US FICA payroll taxes total 15.3% of wages, with employers paying half (7.65%) and withholding the other half from employee pay. A 1099 contractor pays the full 15.3% self-employment tax on net earnings.

A typical US contractor-to-employee conversion takes 10-20 business days once you factor in background checks, I-9 verification, and benefits enrollment windows. That's if everything goes smoothly and nobody's on vacation.

EU and UK companies often hit the conversion trigger around 6-12 months, especially when the contractor follows a fixed schedule and takes daily direction from a manager. That's when your US counsel starts getting nervous about classification risk.

Converting to W-2 status means the employer withholds federal and state income taxes, pays employer portions of FICA, and provides statutory coverage including workers' compensation and unemployment insurance.

Health coverage typically starts on the first of the month after hire or following a 30-60 day waiting period. Pick the wrong conversion date and someone waits an extra month for their benefits to kick in.

What Does Contractor Conversion Mean in the USA?

Contractor conversion moves someone from 1099 independent contractor to W-2 employee. You stop paying them like a vendor and start treating them like staff: withholding taxes, providing workers' comp and unemployment insurance, and applying your employee handbook. They go from invoice to payroll.

A 1099 independent contractor is a non-employee service provider paid gross without payroll withholding. They handle their own federal and state income tax payments and self-employment taxes. A W-2 employee is a worker treated as an employee for federal and state payroll purposes, meaning the employer withholds income taxes, withholds and matches FICA taxes, and reports wages on Form W-2.

The distinction matters because misclassification brings real pain. The IRS, Department of Labor, and state agencies can hit you with back taxes, penalties, and interest when they decide you got it wrong. Beyond the money, you're stuck with duplicate records, broken reporting, and no clear picture of who works where under what arrangement.

How Is Contractor Conversion Different from Temp-to-Perm or Contract-to-Hire?

People mix these terms up all the time, which leads to wrong paperwork, surprise fees, and confused workers wondering why their first paycheck looks different.

A staffing temp-to-perm conversion differs from a 1099-to-W-2 conversion because the worker is typically already a W-2 employee of the agency. The legal change is the employer of record rather than contractor status. A conversion fee is a contractual charge in a staffing or agency agreement that becomes payable if you hire a supplied worker within a defined period. It's not inherently part of a direct 1099-to-W-2 conversion.

Why Do Companies Convert Contractors to Employees?

Companies convert contractors for two main reasons: to reduce legal risk and to keep good people. Usually it's both at once.

Misclassification Risk Reduction

When contractors start looking like employees, you're building risk. The Department of Labor checks who controls the work, who pays for equipment, and what the relationship really looks like. If your contractor uses your laptop, works your hours, only works for you, and takes daily direction from your managers, you're no longer buying a service. You're managing an employee.

When you realise you've been treating a contractor like an employee, you need to fix it fast, recent DOL cases have recovered over $319,000 in back wages for misclassified workers.

Retention and Engagement

Contractors who've been with you for years often want the stability of employment. Benefits eligibility, paid time off, and career development pathways matter to people building their lives around your company. Converting strong performers signals investment in the relationship.

Security and IP Control

W-2 employees typically sign more comprehensive confidentiality and IP assignment agreements than contractors. For companies in regulated industries or those handling sensitive data, the employment relationship provides clearer legal frameworks for protecting intellectual property.

Customer and Procurement Requirements

Some enterprise customers won't let contractors touch their projects. Government contracts often specify that only employees can do certain work. Converting contractors can make you eligible for contracts you couldn't bid on before.

What Are the Red Flags That Signal a Contractor Should Be an Employee?

The IRS and DOL look at three main areas when deciding if someone's really a contractor. Here's what catches their attention.

Behavioral Control Factors

Does the company control how the work is done? Key indicators include whether the worker receives detailed instructions about when, where, and how to work. Training provided by the company suggests an employment relationship. If the worker must attend regular meetings, follow specific processes, or get approval before making decisions, these point toward employee status.

Financial Control Factors

Does the worker have a significant investment in their own business? Can they realise profit or loss? Do they offer services to the general market? Contractors typically have unreimbursed business expenses, provide their own tools, and work for multiple clients. When your company provides equipment, reimburses expenses, and represents the worker's primary income source, the financial control factors lean toward employment.

Relationship Factors

What's the nature of the relationship? Written contracts matter, but they don't override reality. Employee benefits, permanency of the relationship, and whether the services are integral to the business all factor into the analysis. A contractor who's been with you for three years, uses your email domain, and is introduced to clients as part of your team looks like an employee regardless of what the contract says.

Once you spot these warning signs, you have a choice: fix it now on your terms or fix it later under audit pressure. Converting proactively lets you control the narrative. You can show the auditor exactly when and why the relationship changed, with all the right documents dated and filed.

How Do You Convert a Contractor to an Employee in the USA?

A realistic contractor-to-employee conversion takes 10-20 business days from decision to first paycheck. Here's what needs to happen, in order.

Step 1: Assess the Role and Confirm Classification Risk

Start by documenting why you're converting this contractor. Pull their agreement, look at how they actually work, and list the factors that point toward employment. Keep this assessment. You'll need it if anyone asks why you made the change.

Bring in your legal team now, not later. They'll assess your actual exposure and tell you if you need to worry about back wages or just fix it going forward. If you have contractors in multiple states, each state has its own rules that could trip you up.

Step 2: Select the Conversion Model

Go with direct W-2 conversion when you'll manage this person like any other employee: regular one-on-ones, team meetings, performance reviews, and daily priorities from their manager. This works best for contractors who've basically been acting like employees already.

Use an Employer of Record when your EU or UK company doesn't have a US entity but needs to put someone on proper US payroll. The EOR becomes the legal employer, handles taxes and benefits, while your managers still direct the work. It's faster than setting up your own US subsidiary.

Convert to an agency model when headcount caps or hiring freezes mean you can't bring them in-house, but you still need to fix the classification risk. The staffing firm becomes the employer while you keep directing the work.

Step 3: Prepare the Employment Offer

Your offer letter needs the basics: salary, start date, when benefits kick in, who they report to, and at-will language where required. Don't just multiply their hourly rate by 2,000 and call it a salary. Factor in what benefits are worth and what the market pays for this role as an employee.

Many companies reduce contractor rates by 10-15% when converting to salary, accounting for benefits and employer taxes. But that's just a starting point. Your actual offer depends on your benefits package value, their current rate, and what similar employees make in your market.

Step 4: Terminate the Contractor Agreement

Close out the contractor relationship completely before starting employment. Send formal termination notice, pay final invoices, and document the end date. No overlap between contractor and employee status, not even one day. Auditors look for clean breaks between the two relationships.

Step 5: Complete New Hire Paperwork

W-2 onboarding includes I-9 work authorization verification, W-4 tax withholding elections, and policy acknowledgments. The I-9 must be completed within three business days of the start date. State-specific forms may also apply depending on where the employee works.

For teams across multiple states or countries, get these details right before the first payroll run: start date, which entity employs them, where they physically work, and their tax elections. Missing any of these means payroll corrections, amended filings, and annoyed employees wondering why their check is wrong.

Step 6: Set Up Payroll and Benefits

Set them up in payroll with the right tax withholding based on their W-4 and where they actually work. This matters because state taxes and unemployment insurance are based on work location, not where your company is headquartered. Get it wrong and you'll be filing corrections for months.

Check with HR about benefits enrollment deadlines. Every company has different waiting periods and enrolment windows. Miss the window and your new employee waits another month for coverage while sending frustrated Slack messages about their insurance situation.

Step 7: Document the Transition

Build a file that tells the conversion story: your initial assessment, the contractor termination, the job offer, their acceptance, and all onboarding forms. Date everything. This packet shows any future auditor that you spotted a problem and fixed it properly, not that you got caught and scrambled.

What Changes on Day One After Conversion?

The day someone becomes an employee, everything changes operationally. Here's what's different starting day one.

Tax Treatment Changes

The employer begins withholding federal income tax, state income tax (where applicable), and the employee portion of FICA (7.65%). The employer also pays the employer portion of FICA (7.65%), federal unemployment tax (FUTA), and state unemployment insurance. Year-end reporting moves from Form 1099-NEC to Form W-2.

Benefits and Coverage

W-2 employees can join your health plan, get workers' comp coverage, and qualify for unemployment if things don't work out. Depending on your size and location, they might also have FMLA rights, COBRA continuation options, and other protections contractors don't get.

Policy Application

Your employee handbook now applies to them. They might need to track time differently. Expenses go through HR instead of accounts payable. They'll probably get a company email, broader system access, and equipment that you wouldn't give a contractor.

IP and Confidentiality

Employee agreements usually claim broader rights to intellectual property than contractor agreements. Work with counsel to update IP assignment, confidentiality terms, and any non-compete clauses that apply in your state.

Should You Convert a Contractor to an Employee?

The right choice depends on how they actually work and what your business needs. Consider these factors.

Choose direct W-2 conversion when the worker is expected to be managed like an employee for more than six months, when the role requires company-controlled working hours or mandatory attendance at internal meetings, or when the current relationship already shows multiple employment-like characteristics.

Choose to keep a worker as a 1099 contractor only when they have meaningful control over how work is done, can work for multiple clients, and provide their own tools, equipment, and business insurance as a bona fide independent business.

If you've already crossed the line, giving them company email, equipment, and treating them like staff for months or years, work with counsel to fix it carefully. You need documentation showing when and why the relationship changed, not just a new contract slapped on an old problem.

When your contractors live in one system, EOR employees in another, and entity payroll somewhere else, you can't see the full picture. You're making expensive employment decisions blind: missing duplicate workers, misaligned costs, and classification risks that multiply across every country where you operate.

How Do You Negotiate Salary During Contractor Conversion?

Every HR leader faces this question during conversion negotiations. Contractor rates and employee salaries aren't apples to apples because the underlying costs are completely different.

As a contractor, the worker pays the full 15.3% self-employment tax, provides their own benefits, and handles their own business expenses. As an employee, the employer covers half of FICA, provides benefits, and handles equipment and expenses.

A rough starting point: take their hourly rate times 2,000 hours, then reduce by 15-25% to account for benefits and employer taxes. But that's just to get you in the ballpark. The real number depends on your benefits value, market rates for the role, and what matters most to the person across the table.

Some contractors will take less cash for good health insurance and stability. Others want maximum flexibility and every tax deduction they can find. Talk total compensation: salary, benefits value, time off, and what employment means for their situation.

Contractor Conversion Checklist for US Employers

Here's what you need to complete for a clean 1099 to W-2 conversion.

• Document the classification assessment and reasons for conversion
• Consult legal counsel on remediation considerations
• Determine the conversion model (direct W-2, EOR, or staffing)
• Prepare and extend the employment offer
• Negotiate compensation considering total value
• Terminate the contractor agreement with final payment
• Complete I-9 verification within three business days of start
• Collect W-4 for federal withholding elections
• Collect state withholding forms for work location state
• Enroll in payroll with correct tax setup
• Coordinate benefits enrolment timing
• Update confidentiality and IP agreements
• Provide policy acknowledgments and handbook
• Issue company equipment and system access
• Document the complete transition for compliance records

‍

When Conversion Is Part of a Larger Workforce Strategy

If you're converting contractors every few months, the problem isn't individual classification decisions. It's your employment model. When you're operating across multiple countries with contractors here, EOR there, and entities elsewhere, these one-off conversions point to a bigger structural issue.

Most companies follow a natural progression as they grow in each market. They start with contractors for flexibility and speed. When compliance risk rises or headcount grows, they move to EOR for proper employment without entity setup.

The benefit? Your people stay in place while the employment structure evolves around them. No re-onboarding every time you change models. No gaps in payroll records or compliance coverage. One consistent view of your workforce instead of three different vendor dashboards that don't talk to each other.

If you're tired of reconciling contractor invoices against payroll reports and EOR statements every month, or making employment decisions without seeing the full picture, we can help. Talk to the experts about consolidating your fragmented employment operations into one clear view.

Getting Contractor Conversion Right

Contractor conversion in the USA means taking someone from 1099 independent contractor to W-2 employee status. Done right, it takes 10-20 business days, involves HR, payroll, legal, benefits, IT, and the hiring manager, and creates a paper trail that protects you in an audit.

Convert because the relationship has become employment, not because it's convenient or cheaper this quarter. The longer you wait after crossing that line, the more evidence builds up: email threads, meeting invites, performance reviews, equipment orders. Fix it now with proper documentation while you control the timeline.

For mid-market companies with global teams, these individual conversions usually point to a bigger problem. When you can't see who's employed where under what model, every conversion becomes a fire drill. Yes, get this conversion right. But also fix the underlying chaos of managing three different systems for what should be one workforce view.

Payroll Mistakes That Surface When Your Team Grows Faster Than Your Controls

Your company added 47 employees across Germany, the Philippines, and the UK last quarter. Payroll ran on time. Nobody complained.

Then the audit letter arrived.

The German tax authority wants documentation for overtime calculations dating back 18 months. Your UK HMRC records show inconsistent National Insurance categories. And the Philippine 13th month salary calculations? Three employees received the wrong amounts, and now you're facing back pay plus employer contributions on the corrections.

This is what payroll mistakes look like in 2026. They don't announce themselves with bounced payments or angry Slack messages. They compound silently in the background while your team focuses on the next hire, the next market, the next deadline. Teamed's payroll operations benchmarks show that a single payroll correction cycle typically consumes 3-8 internal hours across HR, Payroll, and Finance when you include root-cause investigation, recalculation, approvals, employee communications, and reissuing payslips.

When you're managing contractors, EOR employees, and owned entities across multiple countries, payroll mistakes can quickly hit four figures. Take a single underpayment: you'll pay the missing wages, plus employer social contributions on the correction amount, plus any late payment interest, plus the cost of reprocessing everything. All in the same month.

What Payroll Errors Actually Cost You Each Month

• A single payroll correction typically takes 3-8 hours of internal time across HR, Payroll, and Finance based on what we see with our clients
• When payroll changes come through email or spreadsheets, you're looking at an extra 10-30 minutes per employee each month just managing the updates
• UK employers must keep PAYE records for at least 3 years from the end of the tax year, making audit trails a compliance requirement
• Medium and large UK businesses face HMRC lookback windows of up to 6 years for tax errors
• If you're switching providers and have complex pay structures, expect to run parallel payrolls for 1-2 full cycles to catch any discrepancies
• Bank file errors mean scrambling to fix payments the same day, since UK BACS and EU SEPA cut-offs give you hours, not days, to correct mistakes

The Payroll Mistakes That Show Up in Audits

The payroll mistakes that create four-figure and five-figure exposure share a common pattern: they're invisible until they're expensive. Unlike a missed payment that triggers an immediate employee complaint, these errors accumulate across pay periods, jurisdictions, and employment models.

We're talking about errors in pay calculations, tax withholdings, social contributions, or statutory filings that cost you real money. Not just the penalties and back pay, but the hours your team spends fixing them and the trust you lose with employees.

The mistakes we see hit hardest: misclassifying contractors as employees (or vice versa), botching overtime calculations, getting tax withholdings wrong, missing filing deadlines, forgetting pension deductions, miscalculating holiday pay, and making manual adjustments without proper documentation.

Employee Misclassification

Misclassification is the compliance failure that occurs when a worker is treated as a contractor despite operating under conditions that regulators associate with employment, such as control, integration, and economic dependence. UK IR35 rules require medium and large organisations to make and document contractor status determinations, and HMRC can assess unpaid tax and NIC with potential lookback periods of up to 6 years.

The exposure calculation isn't just the tax differential. It includes employer National Insurance contributions you should have paid, potential penalties, interest, and the administrative cost of reclassifying workers mid-engagement.

Overtime and Wage Calculation Errors

Overtime errors compound quickly because they affect multiple pay periods before anyone notices. The root cause is usually disconnected time tracking, where hours logged in one system don't flow automatically into payroll calculations. In Germany, works councils can have codetermination rights over certain working-time arrangements, which can delay time-tracking changes and indirectly increase payroll error risk if controls aren't agreed early.

Tax Withholding Mistakes

Incorrect tax withholdings create liability on both sides. Underwithhold, and you face penalties plus the awkward conversation with employees about back taxes. Overwithhold, and you've created cash flow problems for your team and administrative burden for corrections.

Across EU member states, statutory leave entitlements and public holiday treatment vary materially by jurisdiction. Applying home-country leave rules to cross-border employees is a recurring root cause of PTO payout and accrual errors.

How Do Payroll Mistakes Become Four-Figure Problems?

The cost framework for payroll errors has five layers that stack on top of each other. Understanding this structure helps you prioritise which controls matter most.

Direct penalties and interest form the first layer. Late payroll tax deposits can trigger penalties ranging from 2-15% depending on how late the payment arrives. HMRC, the IRS, and equivalent authorities across Europe apply escalating penalty structures that punish repeat offenders more severely.

Back pay and corrections create the second layer. When you underpay an employee, you owe the difference plus employer contributions on that difference. In jurisdictions with mandatory social insurance, the employer portion can add 15-30% to the correction amount.

Reprocessing time is the third layer that organisations consistently underestimate. Teamed's process assessments show that manual payroll input workflows commonly add 10-30 minutes of handling time per employee per month when changes are collected by email or spreadsheets rather than system-to-system sync. Multiply that by the number of corrections, and you've consumed significant HR and Finance capacity.

Employee relations costs form the fourth layer. A two-day payroll delay can trigger measurable employee support load because most payroll-related query spikes occur within 48 hours of payday and concentrate in "missing payment" and "wrong tax" tickets. Beyond support tickets, payroll errors erode trust and contribute to turnover risk.

Audit and legal exposure is the fifth layer. In the UK, employers must keep payroll records for at least 3 years from the end of the tax year, which makes searchable audit trails and retrievable registers a compliance requirement rather than a convenience. When disputes arise, you need to prove who approved what, when, and why.

What Causes These Payroll Mistakes in the First Place?

Every payroll mistake traces back to a root cause. Identifying the root cause matters because it determines which control will prevent recurrence.

Manual data entry causes errors because humans make mistakes, especially when copying information between systems or transcribing from emails. The error rate increases with volume and complexity.

Disconnected time tracking means someone exports hours every pay period, manipulates them in Excel, then uploads to payroll. Each manual step is a chance for overtime to go missing or get doubled.

Stale tax tables cause withholding mistakes because tax rates change and systems don't always update automatically. If your payroll platform relies on manual rate table maintenance, you're carrying ongoing defect risk.

No approval workflow means changes to payroll-impacting data happen without oversight. When more than 10 people can change salary, bank details, time, or commissions without approval, you've created both fraud risk and untraceable error risk.

No exception alerts means outlier changes slip through unnoticed. A duplicate bank account, an unusual net pay variance, or an unexpected overtime spike should trigger review before the pay run finalises, not after.

Vendor sprawl is the operational state where payroll, time tracking, benefits, contractor payments, and compliance advisory are split across multiple providers. This increases manual reconciliation and the likelihood of inconsistent employee data.

Which Payroll Controls Prevent Each Mistake?

A payroll platform with built-in approvals and audit logs can show exactly who approved each change and when. Try reconstructing that from email threads six months later when HMRC asks about a suspicious payment.

Exception reporting is a payroll control that automatically flags outlier changes for review before a pay run is finalised. This includes unusual net pay variance, duplicate bank accounts, negative net pay, or unexpected overtime spikes.

What Should a Modern Payroll System Actually Do?

Choose a unified payroll and workforce platform when your company operates in 5+ countries and payroll inputs currently arrive from three or more systems or spreadsheets. The consolidation eliminates reconciliation overhead and reduces the data inconsistencies that cause errors.

Choose automated tax and social contribution updates when your payroll relies on manual rate table maintenance or ad hoc "check the rules" steps. That process doesn't scale past roughly 200-300 employees without recurring defects.

Choose configurable approval workflows when more than 10 people can change payroll-impacting data. Uncontrolled edits increase both fraud risk and untraceable errors.

Choose system-to-system time-to-payroll sync when overtime or shift premiums affect pay for 20% or more of your workforce. Manual imports create version-control risk each pay cycle.

A unified global employment partner differs from a payroll-only vendor because it can align worker classification decisions with payroll execution instead of treating classification as an external assumption. This matters because misclassification is often the most expensive payroll mistake, and it happens before payroll even runs.

Who Is Responsible for Payroll Mistakes?

The short answer: the employer. Even when you outsource payroll processing to a third party, the legal responsibility for correct tax withholdings, timely filings, and accurate employee payments remains with your organisation.

This creates an uncomfortable reality for mid-market companies. You're accountable for compliance across every jurisdiction where you employ people, but you may not have the in-house expertise to verify that compliance is actually happening.

The practical solution is building relationships with partners who have genuine in-market expertise, not just operational capabilities. When your German payroll provider can explain works council implications and your UK provider understands IR35 nuances, you're better positioned to catch problems before they become expensive.

In our experience working with mid-market companies, those with the cleanest payroll operations have simplified their vendor relationships. They work with one partner who sees the complete picture: contractors, employees, entities, compliance. When questions arise, they get consistent answers from someone who understands their full setup.

What Are the Warning Signs Your Current Process Is Creating Risk?

If you recognise any of these situations, payroll errors are probably one audit away from landing on your desk:

Variable pay arrives via spreadsheet. Picture this: sales sends their commission spreadsheet on Thursday. HR updates it Friday morning. Finance finds an error Friday afternoon. By Monday, three versions exist and someone gets paid from the wrong one.

Approvals happen in email threads. Six months later, when auditors ask who approved that salary increase, you're searching through email threads trying to piece together the decision. Half the people have left. The email trail goes cold.

Tax tables are updated manually. Miss one update and you've got systematic withholding errors affecting everyone for two full pay cycles before someone notices.

Overrides happen without logging. Manual adjustments should be rare. When they're common and nobody documents why they happened, you can't explain them during an audit. "I don't know why we paid that amount" isn't an answer HMRC accepts.

You manage 3+ payroll vendors. Different cut-off dates, different approval processes, different report formats. Someone misses the UK deadline because they're focused on the German one. Nobody owns the global reconciliation. Errors hide in the gaps between vendors.

How Do You Migrate to a Better Payroll System Without Creating New Errors?

Running parallel payrolls for 1-2 cycles lets you catch discrepancies before they affect employees. Check net pay matches, verify tax calculations align, and confirm the statutory reports contain everything HMRC or local authorities require.

The migration itself is a high-risk period for payroll errors. Bank file or payment instruction errors frequently create same-day operational firefighting because most payroll payment cut-offs for UK/EU banking rails are measured in hours, not days, once a BACS or SEPA file is released.

A clean migration starts with validating your data before the first parallel run. Set up approvals that match how your team actually works. Configure alerts for the specific issues that matter for your workforce: large overtime payments, international transfers, backdated changes.

The companies that migrate successfully treat the transition as a compliance project, not just a technology implementation. They document the evidence trail from day one, knowing that the first audit question will be "show me who approved this change."

What Evidence Should Your Payroll System Produce?

When HMRC comes calling or an employee disputes their pay from six months ago, you need specific evidence that many payroll systems don't automatically keep.

Change logs show who modified payroll inputs, what changed, and when. This matters because "I don't know who changed that" is not an acceptable answer during an HMRC enquiry.

Approval history demonstrates that changes went through proper authorisation. This is your defence against both fraud allegations and honest mistakes.

Versioned payroll registers let you reconstruct what the payroll looked like at any point in time. When an employee disputes a payment from 18 months ago, you need to show exactly what was calculated and why.

Filing confirmations prove that statutory reports were submitted on time. Late filing penalties are entirely avoidable with proper documentation.

Exception reports show what was flagged for review and how it was resolved. This demonstrates that your controls are actually functioning, not just configured.

Building Controls Before the Next Audit

I've noticed something about companies with clean payroll operations. They run the same checks every month, even when nothing seems wrong. They review exception reports before approving runs. They document decisions as they make them, not six months later when auditors ask. It's not about perfection; it's about catching issues while they're still small.

For mid-market companies managing global employment across multiple platforms, the path forward usually involves consolidation.

Teamed works with mid-market companies to unify fragmented global employment operations into a single advisory relationship and platform. That includes helping you determine the right employment model for each market, whether that's contractors, EOR, or owned entities, and then executing payroll with the controls that prevent the mistakes we've discussed.

If you're spending hours reconciling data across systems or making employment decisions with incomplete information, let's look at your current setup and identify where the breaks typically happen.

The expensive payroll mistakes aren't the obvious ones. They're the small errors that nobody notices until an audit reveals six months of compounded problems. Check your exception reports this month. Your future self will thank you.

Your First U.S. Payroll: What Actually Matters When You're Hiring from Abroad

Your first U.S. payroll run sits somewhere between a compliance exam and a cash flow exercise, and most guides treat it like neither. They walk you through the theory of withholding taxes without telling you that your first direct deposit won't clear if you haven't prenoted your bank account four business days earlier. Or they list the forms you need without mentioning that California requires final pay on the termination day while Texas gives you six days.

Running payroll in the USA requires an Employer Identification Number from the IRS, state tax registrations in every state where employees work, completed W-4 and I-9 forms for each hire, and a funding workflow that moves money before payday arrives. For mid-market companies expanding from the UK or EU, the complexity multiplies when you're managing U.S. payroll alongside contractors in one system, EOR employees in another, and owned entities somewhere else entirely.

I'll walk you through exactly what needs to happen before your first U.S. payday, what can go wrong during that first run, and how to close the books cleanly so you're not scrambling when the auditors show up.

What Tends to Bite First-Time U.S. Payroll

U.S. payroll means you're responsible for calculating net pay, withholding the right taxes at federal, state, and sometimes local levels, then filing returns that prove you did it correctly. Get any piece wrong and the penalties start immediately.

Miss an IRS tax deposit deadline and you'll pay 2% to 15% in penalties on top of what you owe. That's real cash out of your operating budget because someone forgot to check the calendar.

Your bank may take 2 to 4 business days to process that first ACH payroll transfer. Plan for it, or your employees won't get paid on time.

U.S. employers must generally retain Form I-9 records for 3 years after the date of hire or 1 year after employment ends, whichever is later.

From our experience with mid-market companies expanding from Europe, you'll need 2 to 6 weeks to get all your tax registrations sorted before that first payday. The IRS moves slowly, and state agencies move even slower.

U.S. overtime under the FLSA is calculated at 1.5 times the employee's regular rate of pay for hours worked over 40 in a workweek for non-exempt employees.

The Registrations and Paperwork That Gate Your First Payday

You cannot run a compliant U.S. payroll without completing specific registrations and collecting mandatory employee documentation first. Missing any of these creates immediate compliance exposure and can delay your first pay run by weeks.

Start Here: Your EIN from the IRS

An Employer Identification Number is the U.S. federal tax identifier that the IRS issues to an employer and that is required to report and remit federal payroll taxes. You can apply online through the IRS website and receive your EIN immediately if you have a U.S. address and responsible party with a Social Security Number or Individual Taxpayer Identification Number.

Foreign companies without a U.S. presence face a longer timeline. The IRS requires Form SS-4 submitted by fax or mail, and processing takes 4-6 weeks. This single registration often determines whether your first payroll runs on schedule or slips by a month.

The Remote Work Trap: State Registrations

Federal payroll tax compliance differs from state payroll tax compliance because federal obligations are administered by the IRS under a single EIN framework, while state obligations require separate registrations and filings in each state where employees work. If you have employees in California, Texas, and New York, you need three separate state withholding registrations and three separate SUTA accounts.

A common first-payroll error pattern is missing state tax setup for remote hires. Teamed flags multi-state work location mapping as a mandatory pre-payroll control for any company with employees in 2 or more U.S. states. The employee's work location, not your company headquarters, typically determines which state's withholding and unemployment rules apply.

The Forms That Can't Wait: Day 1 and Day 3 Deadlines

A Form W-4 is the U.S. employee withholding certificate that instructs an employer how to calculate federal income tax withholding from an employee's wages. Without a completed W-4, you must withhold at the highest rate, which creates employee dissatisfaction and administrative corrections later.

A Form I-9 is the U.S. work authorization verification record that employers must complete for each employee by reviewing acceptable identity and work eligibility documents. Section 1 must be completed by the employee's first day of work, and Section 2 must be completed within three business days of the start date. There's no grace period here, and penalties for I-9 violations range from $288 to $2,861 per form for first offences.

Setting Up the Mechanics: Pay Schedule, Bank Account, and Pay Types

With your registrations done and paperwork in hand, you need to set up how money actually moves from your account to employees' pockets, plus all the reports and filings that prove you did it right.

Biweekly vs. Monthly: What Works for Your Team

U.S. employers can choose weekly, biweekly, semi-monthly, or monthly pay schedules, but state laws often restrict options. California requires semi-monthly or more frequent pay for most employees. Some states mandate specific pay dates relative to the work period.

Choose a biweekly pay schedule when most employees are hourly or overtime-eligible, because biweekly cycles align more cleanly to timekeeping approval and reduce mid-cycle corrections compared to monthly cycles. The 26 pay periods per year also simplify overtime calculations since each period covers exactly two workweeks.

Why Your CFO Wants a Separate Payroll Account

Choose a separate payroll funding account when your CFO requires tighter cash control, because isolating payroll cash reduces the risk that operating payments cause payroll returns or late tax deposits. This is particularly important for UK-based finance teams managing U.S. payroll remotely.

Your bank needs to prenote your account before the first ACH transaction clears. This verification process confirms the routing and account numbers are valid and typically requires 2-4 business days. Schedule your prenote at least one week before your first intended payday.

Setting Up Pay Types and Deductions

Your payroll system needs earnings codes for regular pay, overtime, bonuses, and commissions. Each code carries different tax treatment, and misconfigured codes create errors that compound across every pay period until corrected.

Pre-tax deductions like 401(k) contributions and health insurance premiums reduce taxable wages. Post-tax deductions like garnishments and Roth contributions come out after taxes are calculated. The sequencing matters for compliance and for your employees' net pay.

First Things First: Getting Employee Data Right

Before your first payroll run, validate every employee record against a complete dataset checklist. For a first U.S. payroll run, Teamed's implementation checklists assume 10-15 minutes per employee to validate a complete dataset including legal name, Social Security Number, address, W-4 elections, I-9 status, and bank details when data is already collected.

The legal name must match the Social Security card exactly. Middle name variations, hyphenation differences, and nickname usage all create W-2 mismatches at year-end that trigger IRS notices. Verify against the actual Social Security card, not the employee's recollection.

Bank account details require the routing number, account number, and account type. Many employees confuse their routing number with their account number, and a single digit error means a returned payment and a missed payday. Consider requiring a voided check or bank letter for verification.

Getting the Numbers In: Hours, Salaries, and Those Tricky Bonuses

A pay period differs from a workweek because a pay period is the employer's payroll cycle for paying wages, while the FLSA overtime threshold is assessed per workweek regardless of the pay period length. If your biweekly pay period spans two workweeks, you must calculate overtime separately for each workweek, not across the full pay period.

For salaried exempt employees, enter the salary amount divided by the number of pay periods. For hourly employees, enter actual hours worked including any overtime hours. Your system should automatically apply the 1.5x multiplier for hours over 40 in a workweek, but verify this calculation manually for your first few pay runs.

One-time payments like signing bonuses or commission payouts require careful tax treatment. Bonuses can be taxed using the percentage method at a flat 22% federal rate or aggregated with regular wages. The method you choose affects the employee's net pay and their perception of your payroll accuracy.

From Gross to Net: Where the Money Goes

Gross-to-net payroll differs from payroll tax filing because gross-to-net is the calculation that determines an individual's net pay on a pay date, while filing is the reporting and remittance process to federal and state agencies on prescribed schedules. Your payroll system handles gross-to-net automatically, but you need to understand the components to catch errors.

FICA taxes are U.S. payroll taxes that fund Social Security and Medicare and that are withheld from employees and matched by employers. The employee pays 6.2% for Social Security on wages up to $184,500 in 2026 and 1.45% for Medicare on all wages. You match both amounts, making your total FICA cost 7.65% of wages.

Federal income tax withholding depends on the employee's W-4 elections, filing status, and pay frequency. State income tax varies dramatically. Nine states have no state income tax, while California's top rate exceeds 13%. Your system must apply the correct state's withholding tables based on where the employee works.

The Last Quiet Moment Before Money Moves

Never approve a payroll without reviewing the gross-to-net summary for each employee. Look for anomalies: negative net pay, unusually high or low tax withholding, missing deductions, or significant changes from the prior period.

A practical first-payroll control standard is to reconcile 100% of employee net pay plus employer taxes to the payroll funding account on payday. Teamed recommends treating any unreconciled difference above 0.5% of gross payroll as an exception requiring investigation.

For your first payroll, build in an extra day for review. Errors caught before submission are corrections. Errors caught after submission become amendments, voids, and off-cycle payments that consume far more time and create compliance documentation requirements.

When the Money Has to Move (and Why Banks Don't Care It's Payday)

Your payroll funding must clear before the pay date. If you're using ACH direct deposit, initiate the funding transfer at least 2-3 business days before payday. Wire transfers clear faster but cost more and may not be practical for recurring payroll.

Direct deposit is the standard for U.S. payroll, but you must accommodate employees who don't have bank accounts, 4.2% of U.S. households remain unbanked.

Paper checks remain an option, though some states require employers to offer direct deposit. Payroll cards provide a third alternative for unbanked employees.

Pay stubs must include specific information depending on the state. California requires detailed itemization of hours, rates, deductions, and accrued leave balances. Other states have minimal requirements. Configure your system to generate compliant pay stubs for each state where you have employees.

After Payday: The Part That Triggers Penalties If You Ignore It

Running payroll doesn't end when employees receive their pay. The post-payroll closeout process determines whether you stay compliant and audit-ready.

When Tax Money Must Hit the IRS (and What Happens If It Doesn't)

Federal payroll taxes must be deposited on a schedule determined by your total tax liability. New employers typically start as monthly depositors, meaning taxes must be deposited by the 15th of the following month. Once your liability exceeds $50,000 in a lookback period, you become a semi-weekly depositor with much tighter deadlines.

State deposit schedules vary. California requires deposits within specific timeframes based on your deposit schedule assignment. Texas has no state income tax but still requires unemployment tax deposits. Track each state's requirements separately.

Quarterly filings include Form 941 for federal taxes and equivalent state forms. Annual filings include Form 940 for federal unemployment tax and W-2s for each employee. Missing these deadlines triggers penalties that compound quickly.

Closing the Loop So Finance Stops Worrying

A payroll closeout is the post-pay-period control process that reconciles payroll outputs to general ledger, validates tax liabilities and payments, and documents any corrections to keep payroll audit-ready. Complete this process within 48 hours of each pay date while details are fresh.

Reconcile your payroll register to your bank statement. The total net pay plus tax payments should match your funding transfer exactly. Investigate any discrepancy immediately, as small errors often indicate systemic issues.

Retain payroll records according to federal and state requirements. The IRS generally limits the assessment period for additional payroll taxes to 3 years from the date a return is filed, but the window extends to 6 years if income is understated by more than 25%. State retention requirements may be longer.

When Things Go Sideways: Late Pay, Wrong Tax, and Emergency Checks

Payroll errors happen. The question is how quickly and cleanly you correct them.

Regular payroll follows your normal schedule. Off-cycle payroll is everything else: fixing mistakes, final paychecks for departing employees, or emergency payments. They need special handling and usually cost more.

Choose to run an off-cycle payroll when a correction materially changes net pay and waiting until the next scheduled payroll would cause wage payment timing risk under the applicable state law. California's requirement for immediate final pay on termination means you'll run off-cycle payments more frequently than in states with longer timelines.

Voiding a payment reverses the entire transaction and requires reissuing a corrected payment. Adjustments on the next regular payroll work for small errors but create employee confusion and may violate state timing requirements for larger amounts.

Remote Employees Create State Tax Accounts (Fast)

If someone works in a different state than your headquarters for more than a few days, you probably need to register there. States want their tax money based on where the work happens, not where your company sits.

High-complexity states like California and New York have significantly more complex requirements than other states. California requires meal and rest break compliance, final pay on termination day, and extensive leave entitlements. New York has its own withholding tables and paid family leave requirements.

Consider staying on EOR longer if you have fewer than 5 employees per state or if employees are spread across 5 or more states. The multi-state compliance burden often exceeds the cost savings of running payroll directly until you reach meaningful headcount concentration.

The Real Decision: Entity vs. EOR vs. Contractor

Choose an Employer of Record when you need to hire in the U.S. without forming a U.S. entity and you want the EOR to be the legal employer responsible for payroll tax filings and employment compliance.

Choose running payroll through your own U.S. entity when you already have a U.S. corporation or LLC registered to employ staff and you can register for federal and state payroll tax accounts in every state where employees work. This gives you direct control but requires internal expertise or outsourced payroll processing.

For UK-based finance teams paying U.S. employees, U.S. wage payments must generally be made in accordance with the employee's state wage payment rules, which can impose different pay frequency and final pay timing requirements by state even when payroll is centrally managed from Europe. EU and UK employers using a U.S. EOR should confirm which party is the employer of record for U.S. wage statements and tax forms, because the legal employer is typically the party responsible for issuing Form W-2s and maintaining payroll tax accounts.

Setting Yourself Up for Calm Paydays

Your first U.S. payroll establishes patterns that persist for years. Invest the time upfront to configure systems correctly, validate employee data thoroughly, and document your processes clearly. The 2-6 weeks of preparation before your first pay run prevents months of corrections afterward.

For mid-market companies managing global employment across multiple platforms, U.S. payroll adds another layer to an already fragmented landscape. If you're already juggling contractors in one system, EOR employees in another, and owned entities elsewhere, adding U.S. payroll complexity compounds the challenge of maintaining visibility and control.

When you're ready to consolidate fragmented global employment operations into a single advisory relationship, talk to the experts at Teamed. We help mid-market companies determine the right employment model for each market, including whether to run U.S. payroll directly or use an EOR, and execute that strategy with compliance confidence across 180 countries.

Post-Acquisition Employment Compliance: What to Fix First in 2026

You've just closed the deal. The champagne's been poured, the press release is out, and now someone in HR is staring at a spreadsheet wondering which of the acquired company's employment practices need to change by Monday.

Acquisitions create a compliance pressure cooker that most mid-market companies aren't prepared for. The acquired workforce brings its own employment contracts, benefit structures, classification decisions, and policy gaps. Your existing compliance framework wasn't built for this. And the 2026 regulatory environment across US states has only made the stakes higher.

Teamed is the unified global employment partner for mid-market companies managing international teams across multiple platforms, vendors, and employment models. We've guided companies through post-acquisition employment integration across dozens of jurisdictions, and the pattern is consistent: companies that prioritise the right compliance changes first avoid the costly remediation that catches everyone else six months later.

The Non-Negotiables in Week One

If you've got people in 10 states, that's 10 different minimum wage rates to track, plus whatever Seattle, Denver, or San Francisco decided to add on top. Seattle's minimum wage reaches $21.30 per hour in 2026. Your payroll team needs those wage tables updated yesterday.

The Fair Labor Standards Act sets a federal minimum wage of $7.25 per hour and requires overtime at 1.5 times the regular rate for non-exempt employees for hours worked over 40 in a workweek.

Form I-9 must generally be retained for 3 years after the date of hire or 1 year after employment ends, whichever is later. Recent ICE enforcement in Denver resulted in over $8 million in fines for employment verification violations.

Once you hit 15 employees, Title VII kicks in. When the EEOC investigator asks for harassment training records and you can't produce them, that missing spreadsheet becomes expensive fast. The EEOC secured over $469.6 million in monetary relief during FY 2024's administrative process alone.

The Affordable Care Act employer shared responsibility provisions generally apply at 50 or more full-time equivalent employees.

Keep payroll records for 3 years minimum under FLSA, wage calculations for at least 1 year. Missing records in a wage audit means you lose negotiating leverage before discussions even start.

What Employment Compliance Issues Surface First After an Acquisition?

Worker classification errors represent the highest-risk compliance gap in most acquisitions. The acquired company's contractor relationships were structured under their risk tolerance, not yours. A worker classification audit tests whether each worker is correctly treated as an employee (W-2) or independent contractor (1099) under applicable federal and state tests, recording the facts relied on, the decision owner, and remediation actions.

California, New York, and several other states apply stricter classification tests than federal standards. If the acquired company operated primarily in Texas but you're headquartered in California, those contractor relationships now face scrutiny under ABC test standards they were never designed to meet.

Wage and hour compliance comes next. The acquired company's overtime exemption classifications, meal break policies, and timekeeping practices may not align with your existing framework. The Department of Labor recovered more than $259 million in back wages for wage and hour violations in fiscal year 2025. Multi-state employers face particular complexity because the controlling law typically follows where the employee performs work, not where headquarters sits.

Benefit plan integration creates immediate obligations. If the combined entity crosses the 50 full-time equivalent employee threshold, Affordable Care Act reporting requirements change. Existing benefit plans may need consolidation or termination, each with its own compliance timeline.

How Do You Build a Post-Acquisition Compliance Inventory?

A US employment law compliance inventory is a controlled register of federal, state, and local obligations mapped to each worker population, work location, and business unit. This includes the owner, evidence required, and review cadence for each obligation.

Start by mapping every state and locality where acquired employees perform work. Remote workers create particular complexity because a remote-work nexus assessment must evaluate whether having employees working from a specific state or city creates payroll tax registration, employment law coverage, or notice/posting duties in that jurisdiction.

Federal law creates the baseline, but state and local laws commonly impose higher standards on minimum wage, paid leave, pay statements, and final pay timing based on the employee's work location. A federal-versus-state preemption check confirms whether a state or local rule can lawfully set a higher standard than federal law.

The inventory should capture every employment relationship type: W-2 employees, 1099 contractors, temporary workers, and any workers provided through staffing agencies. Each category carries different compliance obligations and different risk profiles post-acquisition.

What You Need to Prove, Not Just What You Need to Do

A checklist says 'update posters quarterly.' A control map says 'Sarah updates posters every March 1st using the state website links in our compliance folder, saves PDFs with dates, and emails confirmation to Legal.'

Checklists tell you what needs to happen. Control maps tell you who owns it, how it gets done, when it gets reviewed, and what evidence proves it happened. Post-acquisition, you need control maps.

An audit-ready compliance control is a repeatable process step that produces time-stamped evidence suitable for regulator inquiries, litigation discovery, or due diligence. This means your timekeeping rules, posting updates, training assignments, and policy acknowledgements all generate documentation you can produce on demand.

Here's the disconnect I see constantly: the handbook says employees get overtime after 40 hours, but payroll is set to calculate it daily because someone misunderstood California rules three years ago. The handbook is just paper. The payroll settings are what actually happen.

Which Calls Can't Wait Until Quarter-End?

Choose direct US employment when you will hire 10 or more employees in the same state within 12 months or when your industry requires direct control over benefits, safety programmes, or regulated role approvals. The acquisition may have pushed you past these thresholds in specific states.

Choose a US Employer of Record when you need to maintain compliant employment in a state where you don't have payroll registration or HR infrastructure and you need the relationship established in weeks rather than months. This becomes relevant when the acquired company had employees in states where your entity isn't registered.

Only use contractors when it's truly project work: building your website, not running it daily. They need their own LLC, other clients, and real control over how they deliver. If you're telling them when to log on and which meetings to attend, they're probably employees.

Teamed's graduation model provides a framework for these decisions. Companies progress naturally from contractors to EOR to owned entities as their presence in each market matures. Post-acquisition, you're inheriting someone else's progression decisions and need to evaluate whether they still make sense for the combined organisation.

Your First 90 Days: From Chaos to Control

A 30/60/90-day compliance rollout compresses risk reduction into three measurable phases: assessment, remediation, and monitoring. Teamed recommends allocating 2-4 weeks to build the jurisdiction inventory, 3-6 weeks to remediate payroll and policy gaps, and 2-4 weeks to complete manager training and evidence capture.

Month One: Figure Out What You've Got

HR owns the workforce mapping: every employee, contractor, and contingent worker by location, classification, and employment model. Legal owns the contract review: employment agreements, contractor agreements, and any collective bargaining obligations. Payroll owns the wage and hour audit: exemption classifications, overtime calculations, and pay statement compliance by state.

By day 30, you'll know which fires need water now (misclassified contractors in California) versus which can smolder until next quarter (updating your anti-harassment training format).

Month Two: Fix What Can't Wait

Payroll configuration changes happen here. State tax registrations get filed. Benefit plan integration decisions get executed. Worker reclassifications that can't wait get processed with appropriate documentation.

Policy harmonisation begins. You're not trying to unify every policy in 30 days, but the policies that create immediate liability exposure need attention. Harassment prevention training, accommodation request procedures, and leave administration processes typically fall into this category.

Month Three: Build Systems That Last

Manager training gets completed and documented. The Americans with Disabilities Act generally applies to employers with 15 or more employees and requires an interactive process for reasonable accommodations that should be documented from the first request through implementation or denial.

Evidence capture systems get established. Every control in your map should now be generating the documentation you'll need for audits, claims, or future due diligence.

Posters and Notices: Where Teams Get Caught Out

A multi-state posting programme typically requires separate federal, state, and sometimes city postings for wage, safety, and anti-discrimination topics. Teamed recommends treating postings as a quarterly control because state agencies update templates without synchronised release cycles.

The acquired company's posting compliance may have been adequate for their footprint but inadequate for yours. If they operated in three states and you operate in twelve, the combined entity now needs posting compliance across fifteen jurisdictions.

Electronic posting rules vary by state. Some states permit electronic-only postings for remote workers. Others require physical postings at any location where employees regularly report. Your posting programme needs to account for both the acquired company's work locations and any remote workers who may have been overlooked.

Notice requirements extend beyond postings. Pay statement requirements, final pay timing rules, and separation notice obligations all vary by state. California requires final pay on the termination day. Illinois gives you until the next regular payday. Getting this wrong creates individual liability exposure that compounds across every affected employee.

What You'll Be Asked for When Someone Complains (or You're Audited)

Keep a simple list: time records (3 years, in payroll system, owned by Payroll), pay statements (3 years, employee self-service, owned by HRIS), investigation files (7 years, Legal's secured folder, owned by Legal). Know what you have and where it lives.

Time records need to show hours worked, breaks taken, and any overtime calculations. Pay statements need to comply with state-specific itemisation requirements. Leave logs need to track accrual, usage, and any carryover or forfeiture. Accommodation files need to document the interactive process from request through resolution.

Investigation files deserve particular attention. If the acquired company had pending complaints, incomplete investigations, or unresolved harassment allegations, those become your liability. Documentation of how investigations were conducted, what conclusions were reached, and what remedial actions were taken becomes critical evidence.

The federal Family and Medical Leave Act generally applies to private employers with 50 or more employees within a 75-mile radius and provides up to 12 weeks of job-protected leave in a 12-month period for qualifying reasons. Post-acquisition, you need to evaluate whether the combined entity's geographic footprint changes FMLA eligibility for employees who weren't previously covered.

What a Compliance Tool Won't Do for You During Deal Integration

Tools give you checklists. Advisors tell you which classification decision will blow up in California versus Texas. Tools track changes. Advisors explain what those changes mean for your specific situation. Tools generate reports. Advisors stand behind their guidance when things go sideways.

Checklist tools tell you what's required but don't own the execution. Payroll providers handle wage calculations but typically don't advise on classification decisions or policy harmonisation. HRIS platforms centralise employee data but may not track compliance obligations by jurisdiction.

Advisory-led models provide strategic guidance on which employment model fits each situation, then execute the operational details. This matters most during transitions like acquisitions, where the decisions aren't routine and the stakes are highest.

Choose a quarterly classification review when more than 10% of your US workforce is non-employee labour, because changes in supervision level, tools provided, or schedule control can invalidate prior contractor determinations. Post-acquisition, you're inheriting someone else's classification decisions and need to validate them against your own risk tolerance.

If You Only Have One HRBP and a Tired Payroll Lead

Choose a single national policy with state addenda when you operate in 3 or more US states, because state-specific leave, pay statement, and final pay rules typically cannot be enforced correctly through a single uniform handbook.

If you can only address three things in the first 30 days, prioritise worker classification, wage and hour compliance, and I-9 documentation. These create the highest liability exposure and the most immediate regulatory risk.

Choose manager-led training as a tracked control when your US footprint includes states with mandated harassment training for certain employers, because policy text alone does not create defensible compliance evidence. California, New York, Illinois, and several other states have specific training requirements that may not have been met by the acquired company.

Choose an annual pay-practice audit before merit and bonus cycles when you employ staff in pay-transparency jurisdictions, because job posting and pay-range rules can be violated by legacy templates and ad-hoc recruiter outreach.

How This Week's Cleanup Affects Next Year's Hiring Plan

The compliance work you do in the first 90 days shapes your employment model decisions for years. If you discover the acquired company's contractor relationships can't survive reclassification scrutiny, you're making EOR or direct employment decisions under pressure.

Teamed's analysis of post-acquisition integrations shows that companies with unified global employment operations complete compliance harmonisation faster and with fewer remediation costs than companies managing fragmented vendor relationships. The difference isn't just efficiency. It's having a single advisory relationship that understands both your existing compliance framework and the acquired company's gaps.

Mid-market companies often inherit employment structures that made sense for a smaller organisation but create unsustainable complexity at scale. The acquisition is an opportunity to consolidate fragmented operations into a coherent strategy, but only if you approach compliance integration as a strategic exercise rather than a box-checking exercise.

The companies that get this right treat post-acquisition compliance as the foundation for their employment model strategy, not an obstacle to getting back to business as usual. They build control maps that serve them through the next acquisition, not just this one.

If you're navigating post-acquisition employment compliance and want strategic guidance rather than just operational tools, talk to the experts at Teamed. We help mid-market companies make the right structural decisions at every stage, from first contractor to hundredth entity.