Why Your Managers Keep Turning Contractors Into Employees (And How to Stop Them)

Most contractor misclassification doesn't happen when the contract is signed. It happens on a Tuesday afternoon when a manager asks a contractor to attend a mandatory all-hands meeting, cc's them on an internal Slack channel, or sets their working hours for the week.

The contract itself might be airtight. But the daily behaviours of untrained managers create employment signals that no legal document can undo. This is why generic compliance training fails. Your HR team might know the IRS 20-factor test exists. Your managers might understand that contractors "aren't employees." But neither group has been trained on the specific operational decisions that create misclassification exposure every single day.

The most effective way to prevent B2B contractor misclassification is to build role-specific training programs that teach HR, managers, and procurement how classification decisions are made and where they go wrong in daily operations. This guide provides the implementation framework you need, covering the three distinct audiences who require training, the six core modules every program should include, and the rollout sequence that actually works.

What Actually Has to Happen for Training to Work

You need six modules minimum: the legal tests HR has to know, what managers can and can't do, how to document decisions from day one, when to escalate to Legal, how to audit yourself before the DOL does, and the daily interactions that keep you safe.

For companies your size, aim for five to seven quick scenarios each quarter. Just enough to catch the drift that happens when new managers join or old habits creep back in.

Here's your baseline: if a manager sees something off (contractor asking about PTO, scope creeping into employee territory, being told which tools to use), they raise it within 48 hours. No exceptions.

Keep manager training to 20-30 minutes of real scenarios they'll face this week, plus a one-pager they can pull up when they're about to invite a contractor to the team offsite.

Run full training annually, then hit them with five-minute scenarios every quarter focused on where things actually go wrong: performance reviews, team meetings, tool access, schedule control.

Review every contractor annually and whenever their scope changes or contract renews. If you wait for an audit to check, you're already too late.

Why Generic Compliance Training Fails to Prevent Contractor Misclassification

There's a fundamental gap between knowing a rule and applying it in context. A manager who has completed annual compliance training might correctly state that contractors "aren't employees" while simultaneously setting that contractor's work schedule, requiring them to use company-issued equipment, and including them in performance review cycles.

One-size-fits-all training ignores that HR and managers face entirely different classification decision points. HR generalists need to understand legal framework fluency, classification intake processes, and documentation standards. Frontline managers need to understand behavioural boundaries during daily interactions. Treating these as the same training need produces neither outcome.

Compliance modules are typically annual, but misclassification exposure is daily. A manager makes dozens of decisions each week that could create employment signals. Annual training creates a twelve-month gap between learning and application, during which operational drift accumulates unchecked.

What Is Worker Classification Training?

Worker classification training is a structured learning program that teaches HR, managers, and procurement how to distinguish a B2B independent contractor relationship from employment by applying jurisdiction-specific legal tests to day-to-day operating scenarios. In the B2B contractor context, effective training must address three primary legal frameworks: the IRS Common Law 20-Factor Test used in the United States, the ABC Test applied in California, Massachusetts, New Jersey, and other states, and the Economic Reality Test used by the US Department of Labor. For UK operations, training must also cover IR35 rules and Status Determination Statement requirements.

What Are the Three Audiences Who Need Contractor Classification Training?

Effective contractor classification training is not a single program. It's three distinct curricula mapped to three different roles, each with different daily exposure to misclassification risk.

What Should HR Generalists Learn About Contractor Classification?

HR generalists need legal framework fluency, classification intake process mastery, escalation trigger recognition, and documentation standards. Their key scenarios include onboarding a new contractor, receiving a reclassification complaint, and auditing an existing contractor relationship.

The recommended format is an instructor-led workshop combined with a decision-tree job aid. HR owns the classification decision at engagement start, so they need deeper legal knowledge than managers. They also need to understand when a situation exceeds their authority and requires legal counsel involvement.

HR training should cover how to document the classification decision at engagement start, what records to maintain throughout the relationship, and how to conduct periodic classification reviews. Duration should be 45 to 60 minutes for the legal framework module plus 30 minutes for the documentation and intake module.

What Should Frontline Managers Learn About Working With B2B Contractors?

Managers must understand the concept of behavioural control. Specifically, they need to know that directing how a contractor performs their work, not just what outcome to deliver, is the primary signal of an employment relationship. Training should focus on this distinction with real workplace scenarios.

Key scenarios for managers include assigning tasks, giving performance feedback, including contractors in team meetings, and granting system access. The recommended format is scenario-based e-learning lasting 15 to 20 minutes plus a laminated quick-reference card they can keep at their desk.

A manager-led task assignment differs from SOW-based delivery management because task assignment implies how-to control and prioritisation authority, while SOW management focuses on acceptance criteria, delivery dates, and change control. This distinction is the core learning objective for frontline managers.

What Should Procurement and Legal Liaisons Learn?

Procurement and legal liaisons need to understand contract language that reinforces classification, SOW specificity requirements, and vendor agreement review checklists. Their key scenarios include drafting a new contractor agreement, reviewing a renewal, and flagging scope creep.

The recommended format is a live workshop with legal counsel plus an annotated contract template library. Duration should be 45 to 60 minutes. This audience owns the contractual controls that either support or undermine the classification decision made by HR.

What Core Training Modules Should Every Contractor Classification Program Include?

A complete contractor classification training program should include at minimum six modules covering legal frameworks, behavioural boundaries, documentation, escalation, daily operations, and periodic audit skills.

Module 1: Legal Framework Foundations

This module covers the IRS Common Law Test which evaluates 3 categories: behavioral control, financial control, and relationship type, the ABC Test, and Economic Reality Test, explaining when each applies. It should address federal versus state-level variation, flagging that state law often controls and that several states apply the ABC Test, which is significantly stricter than the federal IRS standard.

For UK operations, training must cover IR35 requirements. UK IR35 requires medium and large private-sector clients to issue a Status Determination Statement stating whether IR35 applies and to take "reasonable care" in making the determination. A company is medium if it meets at least two of these thresholds: annual turnover over £15 million, balance sheet total over £7.5 million, or more than 50 employees.

Duration is 45 to 60 minutes. Format is instructor-led or self-paced with assessment. Audience is HR and legal.

Module 2: Behavioural Boundaries for Managers

This module teaches what "control" looks like in practice: scheduling, tools, methods, dress code, and exclusivity requirements. It covers the daily manager behaviours that create misclassification exposure through scenario-based examples.

Duration is 20 to 30 minutes. Format is scenario-based e-learning. Audience is frontline managers.

Module 3: Documentation and Classification Intake

This module covers how to document the classification decision at engagement start and what records to maintain throughout the relationship. It includes a process walkthrough plus template walkthrough.

Duration is 30 minutes. Format is process walkthrough with templates. Audience is HR.

Module 4: Escalation Protocols and Red Flag Recognition

This module covers what triggers an escalation, including scope creep, duration extension, and behavioural drift. It defines who owns the escalation decision and what the SLA is.

Duration is 15 minutes. Format is short video plus decision tree. Audience is all roles.

Module 5: Audit Readiness and Periodic Review

This module teaches how to conduct an internal classification audit. Frequency should be annually or upon contract renewal. It includes a live audit exercise.

Duration is 45 minutes. Format is workshop with live audit exercise. Audience is HR and legal.

Module 6: Contractor Relationship Management in Daily Operations

The daily tightrope: How do you give feedback without performance managing? Include contractors in necessary communications without making them "part of the team"? Set expectations without controlling methods? This module covers what to say, what not to say, and how to handle the awkward moments.

Duration is 20 minutes. Format is scenario-based e-learning plus manager FAQ sheet. Audience is frontline managers.

What Are the Five Daily Manager Behaviours That Create Misclassification Risk?

These five behaviours create the strongest employment signals and should trigger immediate escalation to HR:

1. Setting the contractor's work schedule or hours. When a manager tells a contractor to work 9am to 5pm or requires them to be available during specific hours, this signals employment-level control. The compliant alternative is specifying deliverable deadlines and letting the contractor determine their own schedule. 2. Requiring the contractor to use company-issued tools or equipment exclusively. Mandating that a contractor use your laptop, software licenses, or equipment signals that you're providing the means of production. The compliant alternative is specifying output requirements and letting the contractor use their own tools. 3. Including the contractor in mandatory employee meetings or performance review cycles. When contractors attend all-hands meetings, participate in performance reviews, or receive the same communications as employees, this creates integration signals. The compliant alternative is project-specific meetings focused on deliverables. 4. Providing ongoing, method-level direction rather than outcome-level direction. Telling a contractor how to complete work rather than what outcome to deliver signals behavioural control. The compliant alternative is defining acceptance criteria and milestones in the SOW. 5. Granting the contractor access to internal systems, benefits portals, or employee-only communications. System access expansion is a high-signal integration factor. The compliant alternative is minimum access required for deliverables, with HR and legal approval for any expansion.

If a manager observes any of these patterns, the escalation path should be to HR within two business days. This should not be resolved informally.

How Should You Roll Out Contractor Classification Training Across Your Organisation?

Sequence matters. Train HR and legal before managers. Don't launch simultaneously. HR needs to be ready to answer manager questions and handle escalations before managers start identifying issues.

Tie training completion to contractor onboarding gates. No new contractor engagement should proceed without manager certification. This creates accountability and prevents uncertified managers from creating misclassification exposure at the point of work assignment.

Build a refresher cadence. Full retraining should occur annually. Micro-refreshers lasting five minutes with scenario updates should occur quarterly. This keeps behavioural boundaries top of mind without creating training fatigue.

Create a living resource hub. Decision trees, escalation contacts, and FAQ sheets should be accessible so training doesn't live only in a one-time module. Managers need reference materials when situations arise.

Measure effectiveness by tracking escalation volume, audit findings, and reclassification incidents before and after training rollout. If escalations increase initially, that's actually a good sign. It means managers are recognising issues they previously missed.

Name a classification owner. A single HR Business Partner or Compliance lead should be the point of contact for escalations. Training without a clear escalation path creates learned helplessness. Managers need to know exactly who to call.

Based on Teamed's work with mid-market companies operating across multiple countries, the organisations that successfully prevent misclassification are those that treat classification training as an operational competency, not a legal checkbox. Some companies also explore misclassification protection coverage as an additional risk management layer. The training design problem is distinct from the legal knowledge problem.

Frequently Asked Questions About Contractor Classification Training

What is the most important thing managers need to learn about working with B2B contractors?

Managers must understand the concept of behavioural control. Specifically, directing how a contractor performs their work rather than just what outcome to deliver is the primary signal of an employment relationship. Training should focus on this distinction with real workplace scenarios, not abstract legal concepts.

How often should contractor classification training be refreshed?

Full classification training should be completed annually and whenever a manager takes on a new contractor relationship. Micro-refreshers consisting of short scenario-based updates should be delivered quarterly to keep behavioural boundaries top of mind.

What should HR do if a manager has already been directing a contractor like an employee?

HR should conduct an immediate classification review of that contractor relationship, document the findings, and consult legal counsel before making any changes to the engagement. Abrupt termination or reclassification without legal review can itself create liability.

Does contractor classification training need to cover state-specific rules?

Yes. Several states including California, Massachusetts, and New Jersey apply the ABC Test, which is significantly stricter than the federal IRS standard, with New Jersey alone having assessed more than $10.6 million in misclassification penalties payable to over 12,500 workers since September 2021. Training must address the most restrictive test applicable to each contractor's work location. For UK operations, IR35 rules require specific training on Status Determination Statements.

Who should own contractor classification training in an organisation?

Ownership typically sits with HR, but effective programs require co-ownership with Legal for framework accuracy and Procurement for contract-level controls. A single HR Business Partner or Compliance lead should be named as the program owner and escalation point.

What's the difference between contractor classification training and contractor onboarding?

Contractor onboarding trains the contractor on how to work with your organisation. Classification training trains your internal team on how to correctly categorise and manage that contractor relationship to avoid misclassification. These are separate programs with different audiences and objectives.

How to Keep Your Managers From Slowly Turning Contractors Into Employees

The gap between knowing classification rules and applying them in daily operations is where most misclassification occurs. Generic compliance training addresses the first problem but ignores the second. Role-specific, scenario-based training that maps to actual decision points is what prevents the Tuesday afternoon mistakes that create liability.

For mid-market companies managing contractors across multiple countries, the complexity multiplies. UK IR35 rules, EU subordination concepts, and US state-level variations all require different training content. Teamed's analysis of contractor management across 70+ countries shows that organisations with differentiated training tracks for HR, managers, and procurement experience significantly fewer reclassification incidents than those using one-size-fits-all approaches.

The right structure for where you are means building training programs that match your operational reality. If you're ready to evaluate your current contractor classification approach or need guidance on building a training framework that actually prevents misclassification, talk to an expert who understands the operational nuances across your markets.

7 Global Payroll Implementation Pitfalls That Derail Expansion (And How to Avoid Them)

A UK-based fintech company hits go-live in Mexico. The system is configured, the vendor has signed off, and the first payroll run processes without errors. Then the complaints start. Employees discover their pay dates don't align with Mexican semi-monthly requirements. The aguinaldo calculation is wrong, failing to meet Mexico's requirement of at least 15 days' salary payable before December 20. Within three weeks, the company faces a regulatory inquiry and a wave of employee grievances that stalls their entire Latin American expansion.

This isn't a technology failure. It's a process failure, and it happens with predictable regularity across mid-market companies expanding internationally.

Global payroll implementation fails most often not because of software limitations, but because of gaps in scoping, data readiness, stakeholder alignment, and local compliance mapping. These failures cluster around specific implementation phases, which means you can identify your risk exposure in real time rather than discovering problems after go-live. This guide walks through the seven most common pitfalls, the implementation phase where each surfaces, and the specific steps to avoid them.

What is global payroll implementation? Global payroll implementation is a multi-phase operational programme that configures, integrates, and validates payroll processes across two or more countries, including local statutory rules, data migration, payroll calendars, approvals, and post-go-live governance. It typically spans 3-9 months depending on the number of countries and complexity of the existing HR and finance tech stack.

Quick Facts: Global Payroll Implementation

Global payroll implementations typically take 3-9 months for mid-market organisations operating in multiple countries, with 6-12 months being common when rolling out 10+ markets in phased waves. A practical mid-market data-readiness window is 60 days pre-migration, because most remediation work involves collecting country-specific identifiers and cleaning historical earnings needed for year-to-date calculations. At minimum, one full pay cycle of parallel payroll per new country should be planned as a go-live gate. A reconciliation threshold of 0.5% variance is a workable go/no-go rule for parallel payroll sign-off because it forces root-cause analysis rather than accepting aggregate accuracy. Mid-market global expansion commonly spans 2-15 countries, which increases implementation risk because each additional jurisdiction adds distinct pay calendars, statutory filing deadlines, and local data-field requirements. A steady-state design period of 4 weeks at the end of implementation materially reduces post-go-live incidents.

Why Do Global Payroll Implementations Fail More Often Than They Should?

Most implementation failures aren't random. They cluster around the same root causes: inadequate country-specific compliance mapping during scoping, poor data migration governance, misaligned payroll calendars, insufficient parallel testing before go-live, and the absence of a steady-state operational model after launch.

The pattern becomes clear when you map failures to implementation phases. Scoping failures create compliance gaps that surface months later. Configuration failures corrupt data or misalign calendars. Testing failures let calculation errors reach employees. Go-live failures erode trust in new markets. Steady-state failures turn one-time problems into recurring operational headaches.

Understanding which phase you're in helps you identify which pitfalls you're most exposed to right now. HR leaders on Reddit frequently describe implementation as "lots of moving parts, time pressure, and issues that are tough to solve." The framework below gives you a diagnostic lens to catch problems before they become crises.

Pitfall 1: Underestimating Country-Specific Compliance Requirements (Scoping Phase)

What it is: Treating all countries as variations of the home-country payroll model rather than as distinct legal environments with unique statutory requirements.

Implementation teams often rely on vendor-provided country guides without validating against current local labour law. Legal review gets deferred to post-configuration, which is too late. The result is incorrect statutory deduction logic, missed mandatory benefits like 13th-month pay in the Philippines or Mexico, mandatory severance reserves in Brazil, or non-compliant payslip formats that violate local disclosure requirements.

In the UK, employers must run PAYE and report through Real Time Information submissions to HMRC on or before the date employees are paid. An implementation that cannot generate compliant FPS submissions is not go-live ready. In Germany, payroll implementations must correctly manage employee tax class and church tax applicability, where incorrect class assignment can create withholding variances of up to €11,325 annually on a €50,000 salary. In France, payroll implementations must support a compliant payslip structure and employer/employee social contributions logic.

How to avoid it: Conduct a country-by-country compliance audit before configuration begins. Involve local legal counsel or a country-specific EOR partner at the scoping stage. Build a compliance requirements matrix as a living document that lists statutory deductions, reporting deadlines, payslip rules, required benefits, and payroll calendar constraints, with each requirement tied to an owner, evidence, and the system field that satisfies it.

Pitfall 2: Why Does Poor Data Migration Planning Cause So Many Problems? (Configuration Phase)

What it is: Migrating employee data from legacy HRIS or spreadsheets without a structured data governance process that assigns ownership and validates completeness.

Data migration is frequently treated as an IT task rather than a cross-functional HR, Finance, and Payroll responsibility. No data owner is assigned per country. The consequences include duplicate employee records, missing tax IDs or national insurance numbers, and incorrect historical earnings data that corrupts year-to-date calculations at go-live.

When your source HR data comes from more than one system, field-level ownership becomes essential to resolve conflicting sources of truth. A UK company migrating payroll data needs complete NI numbers for every employee, because payroll may be legally unable to withhold and report correctly without them.

How to avoid it: Run a data audit 60 days before migration. Define a data dictionary with required fields per country. Assign a named data steward per market who owns data quality for that jurisdiction. Run parallel payroll for at least one cycle before cutover to surface data gaps before they affect live employee pay.

Pitfall 3: Misaligned Payroll Calendars (Configuration Phase)

What it is: Applying home-country pay frequency logic to markets with legally mandated or culturally expected pay cycles that differ significantly.

Global payroll calendar design is often owned by the home-country payroll team who default to familiar cadences. A UK company might assume bi-weekly pay works everywhere. But Mexico legally requires semi-monthly payment, with wage-payment intervals no longer than 15 days for most workers. Germany expects monthly payment. The mismatch creates non-compliant pay runs, employee dissatisfaction in new markets, and retroactive corrections that create tax filing complications.

Payroll calendar misalignment differs from payroll calculation misconfiguration in an important way. Calendar misalignment causes late or non-compliant payment timing even when gross-to-net is correct. You can calculate everything perfectly and still violate local law by paying on the wrong date.

How to avoid it: Map legally mandated pay frequencies for every target country during scoping. Build country-specific payroll calendars into the configuration spec before vendor setup begins. Validate that your system can support multiple pay frequencies running simultaneously across different jurisdictions.

Pitfall 4: What Happens When HR and Finance Aren't Aligned? (Scoping to Configuration Phase)

What it is: HR owns the implementation project while Finance and Accounting are brought in late, or vice versa, creating disconnects in GL coding, cost centre mapping, and approval workflows.

Global payroll sits at the intersection of HR and Finance but is rarely jointly owned. Project governance defaults to whoever initiated the vendor contract. The result is GL mapping errors that require manual journal entries every pay cycle, approval workflows that don't match Finance's month-end close calendar, and cost centre structures that don't align with the chart of accounts.

Teamed's analysis of mid-market implementations shows that payroll-to-GL mapping becomes a finance-critical dependency when payroll outputs must post to multiple cost objects. CFOs validating with spreadsheets need clean data flowing from payroll to general ledger without manual intervention.

How to avoid it: Establish a joint HR-Finance steering committee at project kickoff. Include Finance in vendor selection and configuration sign-off. Map payroll outputs to GL requirements before configuration begins. Ensure approval workflows align with month-end close timelines so payroll doesn't create bottlenecks in financial reporting.

Pitfall 5: Skipping or Shortcutting Parallel Payroll Runs (Testing to Go-Live Phase)

What it is: Going live on a new payroll system without running it in parallel against the legacy system for at least one full pay cycle.

Timeline pressure, budget constraints, or vendor assurances that the system is "ready" lead teams to skip parallel runs. They're seen as redundant cost. But skipping shifts error detection from controlled testing to employee impact. Calculation errors in net pay, incorrect tax withholdings, or missed deductions aren't caught until employees report discrepancies, at which point corrections require amended filings and erode trust.

Choose a mandatory parallel payroll gate when any of the following are true: variable compensation exists, multiple benefit providers feed deductions, or the go-live period includes statutory year-end or year-to-date resets. These conditions amplify gross-to-net error rates significantly.

How to avoid it: Treat parallel payroll as non-negotiable for every new country go-live. Define a reconciliation threshold where variances above 0.5% require root-cause analysis before go-live approval. Document sign-off criteria in the project plan. At minimum, plan one full pay cycle of parallel payroll per new country, with two cycles often required when payroll includes variable pay or multiple benefit deductions.

Pitfall 6: Underinvesting in Employee Communication (Go-Live Phase)

What it is: Failing to proactively communicate payroll changes to employees in new markets before go-live, including new payslip formats, payment dates, and deduction structures.

Internal communications is deprioritised in technical implementation projects. The assumption is that employees will figure it out. But this creates a spike in payroll-related HR tickets at go-live, employee trust erosion in markets where the company is still building its employer brand, and confusion over new deduction line items that employees interpret as errors.

In the UK, under the Working Time Regulations, most workers are entitled to 5.6 weeks' paid holiday per leave year. If holiday accrual appears differently on new payslips, employees need to understand why before they assume something is wrong.

How to avoid it: Build a country-specific employee communication plan into the implementation timeline. Send pre-go-live payslip explainers that walk employees through what will change and why. Create a dedicated payroll FAQ for each market addressing common questions. Assign a local HR point of contact for the first two pay cycles post-launch to handle questions before they escalate.

Pitfall 7: No Post-Go-Live Steady-State Process Design (Steady-State Phase)

What it is: Treating go-live as the finish line rather than the beginning of an ongoing operational model, with no documented processes for off-cycle payments, new hire onboarding into payroll, leavers, and annual compliance updates.

Implementation energy is front-loaded. Once the system is live, the project team disbands before operational runbooks are written. The result is ad hoc handling of off-cycle runs, missed annual statutory updates like new tax tables or minimum wage changes, and inconsistent onboarding-to-payroll timelines that delay first paychecks for new hires.

Based on Teamed's work with mid-market companies across 70+ countries, a steady-state design period of 4 weeks at the end of implementation materially reduces post-go-live incidents. This is the window where runbooks, country owners, escalation paths, and statutory update monitoring are formally handed over.

How to avoid it: Dedicate the final 4 weeks of implementation to steady-state process documentation. Assign a named payroll ops owner per region. Schedule a 90-day post-go-live review to catch process gaps before they become compliance issues. A 90-day review is a practical control point because it captures the first quarterly statutory updates, late-identified configuration gaps, and recurring operational bottlenecks.

How to Self-Diagnose Your Implementation Risk

Five questions can signal your implementation risk exposure right now.

1. Have you completed a compliance requirements matrix for every target country before configuration began? 2. Is there a named data steward assigned for each country's employee data migration? 3. Does your implementation plan include at least one parallel payroll run per new country? 4. Have HR and Finance jointly signed off on GL mapping and cost centre structure? 5. Does your project plan extend 90 days past go-live with a named steady-state process owner?

If you answered "yes" to 0-2 questions, you're at high risk. Three to four "yes" answers indicate moderate risk. Five "yes" answers means you're well-positioned. This diagnostic helps you identify gaps while you still have time to address them.

What Are the Most Common Reasons Global Payroll Implementations Fail?

The most common reasons global payroll implementations fail include inadequate country-specific compliance mapping during scoping, poor data migration governance, misaligned payroll calendars, insufficient parallel testing before go-live, and the absence of a steady-state operational model after launch. Most failures are process failures, not technology failures. The companies that get it right treat compliance mapping, data governance, and steady-state design as first-class project deliverables, not afterthoughts.

How Long Does a Global Payroll Implementation Typically Take?

A global payroll implementation typically takes 3-9 months, depending on the number of countries, the complexity of the existing HR and finance tech stack, and the readiness of employee data. Single-country implementations for straightforward markets can be completed in 8-12 weeks. Multi-country rollouts spanning 10+ markets commonly require 6-12 months with phased go-lives.

Who Should Own a Global Payroll Implementation Project?

Global payroll implementation is most successful when co-owned by HR Operations and Finance/Payroll, with a dedicated project manager overseeing the implementation timeline. Sole ownership by either HR or Finance alone is a common source of stakeholder misalignment, particularly around GL mapping and approval workflows. A joint steering committee ensures both functions have visibility and sign-off authority at critical milestones.

What Is Parallel Payroll and Why Does It Matter?

Parallel payroll is the practice of running a new payroll system simultaneously alongside the legacy system for one or more pay cycles before full cutover. It matters because it surfaces calculation errors, missing deductions, and data migration gaps before they affect live employee pay. Errors that go live require amended tax filings and erode employee trust in markets where you're still establishing your employer brand.

How Do You Handle Compliance Updates After Global Payroll Go-Live?

Post-go-live compliance maintenance requires a documented process for monitoring and applying annual statutory updates, including new tax tables, minimum wage changes like the UK's £12.71 hourly rate from April 2026, and mandatory benefit adjustments, for each country in scope. Assign a named compliance owner per region and schedule a quarterly review cycle to catch regulatory changes before they affect payroll runs.

Getting Global Payroll Implementation Right

Global payroll implementation failures are predictable and preventable. The companies that succeed treat compliance mapping, data governance, and steady-state design as first-class project deliverables from day one. They establish joint HR-Finance ownership, run parallel payroll without shortcuts, and plan for steady-state operations before the project team disbands.

The right structure for where you are matters as much as the technology you choose. Whether you're implementing payroll across owned entities or working with an EOR partner, the same pitfalls apply. The difference is whether you catch them during scoping or discover them when employees complain about incorrect pay.

If you're planning a global payroll rollout and want to identify your risk exposure before go-live, talk to an expert who can help you map your implementation phases to the pitfalls that matter most for your specific situation.

How to Ensure Accuracy in Payroll Processing

Your payroll ran. Funds went out. Then an employee calls: their check is wrong. Again.

If you've been in HR or finance long enough, you know this feeling. The scramble to identify what went wrong, the off-cycle correction that eats hours of your week, the quiet erosion of trust from the employee who just wanted to be paid correctly. Industry benchmarks from the US Bureau of Statistics and EY suggest that only 80% of payrolls run completely error-free, with an overall accuracy standard of 98.8%. That gap between "mostly right" and "completely right" is where compliance risk, employee frustration, and finance team rework hours accumulate.

Ensuring accuracy in payroll processing requires a layered control system across four stages: data collection, calculation verification, pre-approval auditing, and post-run reconciliation. Each stage has distinct failure points and requires specific ownership by role. Organisations that treat payroll accuracy as a checklist activity rather than a process architecture consistently experience the same categories of errors: incorrect hours, missed deductions, tax miscalculations, and off-cycle corrections that trigger IRS penalty exposure (ranging from 2% to 15% for late tax deposits) and erode employee trust.

This guide is for Payroll Administrators, HR Managers, and Finance Controllers at companies with 50-500 employees who need a repeatable system, not another tip list. You'll find a stage-by-stage control framework, role-specific responsibilities, and a pre-run checklist you can implement this pay period.

Quick Facts: Payroll Accuracy Benchmarks

A practical variance threshold for pre-approval payroll checks in mid-market environments is ±5% on individual gross pay compared with the prior comparable period, according to Teamed's payroll control design guidance for multi-country teams.

A payroll cutoff window of 2 business days before calculation start is a common minimum for organisations with manager-approved time capture, allowing exception resolution without off-cycle payments.

A quarterly internal payroll audit sample of 10-15% of employee records provides statistically meaningful oversight without disrupting business-as-usual operations.

A three-way reconciliation (payroll register to bank file to general ledger) can typically be completed in 60-120 minutes per pay run when the chart of accounts and cost centres are stable.

A dual-approval rule for employee bank detail changes with a 24-hour cooling-off period materially reduces misdirected payment risk in environments with frequent joiners and leavers.

A standard payroll documentation retention period for audit readiness in Europe and the UK is 6 years for payroll registers, approvals, and reconciliation artefacts.

What is payroll accuracy? Payroll accuracy refers to the consistent, error-free calculation and disbursement of employee compensation, including wages, deductions, taxes, and benefits, in full compliance with applicable labour laws and internal policies. High payroll accuracy requires both system-level controls and human verification at defined checkpoints in the payroll cycle.

Why Do Payroll Errors Happen and Where in the Process Do They Originate?

Most payroll errors don't happen during processing. They happen 3 days before it. Understanding where errors enter the cycle is the first step toward building controls that actually catch them.

The Four Stages Where Errors Enter the Payroll Cycle

Stage 1 involves data input: timesheets, new hire data, benefit elections, and pay rate changes. This is where the majority of downstream errors originate. Stage 2 covers calculation logic: tax tables, overtime rules, and deduction sequencing. Stage 3 is the pre-approval review, where missed exceptions and unreviewed changes slip through. Stage 4 is post-run reconciliation, the last chance to catch errors before funds are released.

Preventive controls at Stages 1 and 2 reduce payroll errors earlier and cheaper than detective controls at Stages 3 and 4. Stopping incorrect data from entering the calculation stage costs less than recovering a misdirected payment after settlement.

What Are the Most Common Payroll Error Categories?

The most common cause of payroll errors is inaccurate or incomplete data at the input stage, with 50.61% of payroll professionals citing HR data input errors as a prominent root cause of decreased accuracy. This includes unapproved timesheets, stale employee records with outdated tax withholding or incorrect bank accounts, and missed new hire or termination entries. Incorrect hours and overtime classification follow closely, particularly in organisations with variable pay structures.

Missed or duplicate deductions create compliance exposure, especially when pre-tax deductions like 401k or HSA contributions are applied in the wrong sequence. Tax table misapplication across federal, state, and local jurisdictions compounds quickly in multi-state operations. Off-cycle adjustments processed without audit trails create reconciliation nightmares at quarter-end and year-end.

Step 1: How Do You Establish Clean Data Inputs Before Every Payroll Run?

Data quality is the foundation. If garbage enters the system, no amount of downstream checking will produce accurate payroll. This stage requires hard cutoffs, verified master data, and validated approval chains.

Lock the Payroll Data Cutoff Window

Define a hard cutoff date for timesheet submission and manager approval. No changes accepted after cutoff without a formal exception process that documents who approved the late change and why. A payroll cutoff window of 2 business days before calculation start is a common minimum for organisations with manager-approved time capture.

The exception process matters as much as the cutoff itself. Late changes are a leading driver of off-cycle corrections and duplicate adjustments, with 23.93% of organizations identifying retroactive entries as a prominent cause of payroll inaccuracy. When you allow informal exceptions, you're building a system that rewards procrastination and punishes the payroll team.

What Should You Verify in Employee Master Data Each Cycle?

Every payroll run should include a cross-check against the HRIS change log to maintain payroll data compliance. Confirm new hires are added with correct pay rates, bank details, and tax withholding. Verify terminations are processed with accurate final pay dates. Check that address and tax changes from the prior period have been applied correctly.

The Payroll Administrator owns this verification, but HR provides the source data. When these two systems don't reconcile, errors multiply. A maker-checker approval for bank details, pay rate changes, and one-time payments is essential when payroll inputs can be changed by more than one team.

How Do You Validate Timesheet Approval Chains?

Every hourly employee's timesheet must carry manager digital approval before it enters the payroll calculation. Flag unapproved or zero-hour timesheets as exceptions before processing. Integrating scheduling and payroll systems so hours flow automatically cuts manual entry errors significantly.

Zero-hour timesheets for salaried employees should trigger an exception flag. Either the employee didn't work (which HR needs to know) or the timesheet wasn't completed (which the manager needs to address). Neither scenario should silently pass through to payroll.

Pre-Payroll Data Checklist:

1. Confirm all timesheets are submitted and manager-approved 2. Verify new hires are added with correct pay rates and bank details 3. Confirm terminations are processed with accurate final pay dates 4. Check address and tax withholding changes are applied 5. Validate benefit election changes from open enrollment are reflected 6. Flag any employee with a recent title change for FLSA classification review 7. Confirm all variable pay elements (bonuses, commissions) are documented 8. Verify bank detail changes have dual approval and cooling-off period complete

Step 2: How Do You Build Calculation Verification Into the Workflow?

Once data is locked, the calculation stage introduces its own failure modes. Tax tables go stale. Deduction sequencing gets misconfigured. Overtime thresholds get missed. This stage requires systematic checks, not spot reviews.

Use Gross-to-Net Calculation Audits

Run a variance report comparing current period gross pay to prior period. Flag anything outside the ±5% threshold for investigation before approving the run. A variance-report-driven review differs from a line-by-line payroll register review because it targets outliers above a defined threshold, allowing payroll teams to focus effort where error probability is highest.

Investigate all flagged variances before approving the run. The goal isn't to explain away variances. It's to confirm that each variance has a legitimate cause documented in the system.

How Often Should Tax Tables Be Updated?

Confirm federal, state, and local tax tables are updated at the start of each calendar year and after any mid-year legislative changes. Document the date of last tax table update in the payroll system audit log. In the UK, HMRC Real Time Information rules generally require a Full Payment Submission to be sent on or before the date employees are paid, making pre-run approvals time-critical for compliance accuracy.

Tax table currency is particularly critical in multi-state US operations and multi-jurisdiction European payroll. California and New York have significantly more complex requirements than other states. In Ireland, payroll accuracy controls should include verification that statutory payroll reporting and remittances align to Revenue requirements for PAYE modernisation.

Audit Deduction Sequencing and Overtime Classification

Pre-tax deductions (401k, HSA, FSA) must be applied before taxable deductions. Confirm benefit election changes from open enrollment are reflected correctly. In countries where meal vouchers, mobility benefits, or other in-kind benefits are common, payroll accuracy controls must verify tax and social contribution treatment per benefit type.

Flag all employees who crossed the 40-hour threshold for overtime review. Verify FLSA exempt and non-exempt classification for anyone with a recent title change. Incorrect classification can create retroactive employer liabilities that compound over multiple pay periods.

Step 3: What Should Each Role Verify in the Pre-Approval Audit?

The pre-approval audit is where three roles converge: Payroll Administrator, HR Manager, and Finance Controller. Each owns specific checkpoints. No single role can ensure accuracy alone.

What Should the Payroll Administrator Verify?

The Payroll Administrator owns exception report review: negative net pay, zero-hour salaried employees, first-time direct deposit accounts. A high-signal pre-run exception pack typically includes at least 7 automated flags: negative net pay, zero pay for salaried staff, first payment, bank detail change, unusual overtime, duplicate allowance, and termination paid after leave date.

Headcount reconciliation is critical. Total employees paid this period should match active headcount in HRIS. Discrepancies indicate either ghost employees (fraud risk) or missed terminations (compliance risk).

What Should the HR Manager Approve?

The HR Manager confirms all new hires and terminations processed this cycle are correct. They sign off on any manual adjustments or off-cycle corrections included in the run. This approval creates accountability for the upstream data that HR owns.

HR should also verify that any contract-specific allowances or role-based pay elements are correctly applied. Automated payroll controls catch high-volume pattern errors consistently every run, but manual controls are more effective for contextual judgement on contract-specific situations.

What Should the Finance Controller Validate?

The Finance Controller validates that total payroll liability matches budget forecast within acceptable variance. They confirm funding account balance before ACH release and review GL coding for each payroll cost centre. This is the control CFOs use to validate payroll liability accuracy.

Three-way reconciliation (register-to-bank-to-GL) differs from register-only reconciliation because it validates both cash movement and accounting integrity. The Finance Controller's sign-off should confirm this reconciliation is complete.

Role-based approvals differ from single-owner approvals because they allocate accountability to the teams that own the upstream data (HR), the payroll calculation and exceptions (payroll), and the financial controls (finance). This reduces control gaps at handoffs.

Step 4: How Do You Reconcile After Every Payroll Run?

Post-run reconciliation is your last line of defence. It should be completed before funds are released when your payment method supports pre-funding validation.

The Post-Run Reconciliation Process

1. Pull the payroll register and compare total net pay to prior period 2. Reconcile payroll tax liabilities to your tax deposit schedule 3. Confirm all direct deposit transactions settled with no returns or rejects 4. Tie payroll totals to the general ledger entries for the period 5. Archive the reconciliation report with approver signature for audit trail

A three-way reconciliation can usually be completed in 60-120 minutes per pay run when the chart of accounts and cost centres are stable. Preventing an incorrect payment is lower-cost than recovering it after settlement.

How Often Should Payroll Audits Be Conducted?

Per-run reconciliation should happen every payroll cycle. This is non-negotiable. Monthly reconciliation should tie payroll tax deposits to 941 liability. Quarterly reconciliation should include a W-2/1099 data integrity check. Annual reconciliation should balance year-end W-2 data before filing.

A quarterly internal payroll audit sample of 10-15% of employee records provides statistically meaningful oversight. Audit for correct pay rates, accurate deductions, and proper tax withholding. Track error type, root cause, and corrective action in a payroll error log. Use the log to identify systemic issues versus one-off mistakes.

How Do Manual, Automated, and Hybrid Payroll Controls Compare?

The right control model depends on your team size, payroll complexity, and existing tech stack. Most mid-market companies with 50-500 employees find that a hybrid approach delivers the highest error detection rate with moderate time investment.

Manual controls rely on human review at every step. They work for very small teams under 20 employees but create high time investment of 6-10 hours per cycle. The key risk is human fatigue and inconsistent application across pay periods.

Automated controls flag exceptions automatically through system rules. They work best for teams with standardised pay structures and require only 1-2 hours per cycle for review. The key risk is misconfigured rules that go undetected until an audit surfaces them.

Hybrid controls combine automation for volume errors with human review for edge cases. This approach requires 2-4 hours per cycle and works for most mid-market companies. The key risk is unclear human and system handoff protocols that create gaps in coverage.

Choose a hybrid payroll accuracy model when you have 200-2,000 employees, multiple pay elements like overtime, allowances, bonus, and salary sacrifice, and at least one country with local payroll complexity. Automated exception flags still require human judgement on edge cases.

How Do You Build a Payroll Accuracy Culture on Your Team?

Controls only work when they're documented, reviewed, and improved. A payroll accuracy culture treats errors as learning opportunities, not blame events.

Document Your Payroll Process in a Standard Operating Procedure

Every step, every owner, every deadline should be in writing. Review and update the SOP annually or after any system change. Choose to centralise payroll policy (definitions of overtime, allowances, deductions, and leaver rules) when you have more than 3 business units or cost centres. Inconsistent rule interpretation is a repeatable root cause of payroll processing errors.

A robust payroll calendar for monthly payroll commonly includes 8 distinct milestones: cutoff, manager approval, input validation, calculation run, variance review, approval, bank file release, and post-run reconciliation.

Conduct Quarterly Internal Payroll Audits

Sample 10-15% of employee records each quarter. Audit for correct pay rates, accurate deductions, and proper tax withholding. Choose a quarterly internal payroll audit when you operate in more than one European jurisdiction or use more than one payroll vendor. Control drift and inconsistent local practices are more likely in distributed operating models.

Create a Payroll Error Log and Review It Monthly

Track error type, root cause, and corrective action for every error. Use the log to identify systemic issues versus one-off mistakes. A minimum separation-of-duties control for payroll accuracy is that the person who inputs variable pay should not be the sole approver of the final payroll register. This control is typically achievable with a 2-person workflow in mid-market teams.

Frequently Asked Questions

What is the most common cause of payroll errors?

The most common cause of payroll errors is inaccurate or incomplete data at the input stage, including unapproved timesheets, stale employee records with outdated tax withholding or incorrect bank accounts, and missed new hire or termination entries. Most downstream calculation errors trace back to a data quality problem, not a system failure.

How do you measure payroll accuracy?

Payroll accuracy is typically measured as the percentage of payroll transactions processed without error. Industry standard is 98.8% overall accuracy with 80% of payrolls error-free. Track errors by type (hours, deductions, tax, bank details) and root cause (data input, calculation, approval, reconciliation) to identify systemic issues.

Who is responsible for payroll accuracy in a company?

Payroll accuracy is a shared responsibility across three roles: the Payroll Administrator owns data integrity and exception review, the HR Manager owns new hire and termination accuracy and manual adjustment approval, and the Finance Controller owns liability validation and funding confirmation. No single role can ensure accuracy alone. The control system requires all three checkpoints.

What happens if payroll errors are not corrected promptly?

Uncorrected payroll errors expose the organisation to IRS penalties for tax underpayment or late deposits, state labour law violations for wage underpayment, employee trust erosion, and costly off-cycle correction runs. Errors caught post-filing may also require amended 941s or W-2c forms, with penalties reaching $340 per information return, adding significant administrative burden.

What are the 5 basic steps in processing payroll?

The five basic steps are: collect and validate time and attendance data, calculate gross pay including regular wages, overtime, and variable pay, apply deductions and calculate taxes, process payments through direct deposit or check, and reconcile payroll totals to the general ledger and bank records.

Building Your Payroll Accuracy System

Payroll accuracy isn't about working harder. It's about building a system with layered controls that catch errors at every stage. Data inputs, calculation verification, pre-approval audits, and post-run reconciliation each serve a specific purpose. Skip one, and errors slip through.

The organisations that get this right treat payroll as process architecture, not a checklist. They document their SOPs, conduct quarterly audits, and track errors to identify systemic issues. They assign clear ownership to Payroll, HR, and Finance, with handoffs that don't create gaps.

For mid-market companies managing payroll across multiple countries and employment models, Teamed's analysis of payroll operations across 70+ countries shows that the hybrid control model, combining automated exception flags with human review of edge cases, delivers the highest accuracy with sustainable time investment. If you're ready to build a payroll process that gets it right every time, talk to an expert about how unified global employment operations can support your payroll accuracy goals.

How to Set Up an Entity in the US: A Step-by-Step Guide for Global Companies (Including Payroll)

You've decided to hire in the United States. The market opportunity is clear, the candidate is ready, and your board expects movement. Then reality hits: most guides cover legal registration and stop there. The real operational challenge starts after incorporation, when you're staring at payroll tax registration forms, EIN sequencing dependencies, and state account timelines that nobody warned you about.

This is where international companies lose weeks. A foreign-owned company typically needs 6-10 weeks to go from deciding to form a US entity to running a first compliant US payroll, driven mainly by EIN issuance and state payroll account activation sequencing. That timeline catches most global expansion teams off guard, especially when the candidate you've found expects to start in three weeks.

Setting up a US entity involves seven sequential steps: choosing a legal structure, selecting a state of formation, filing formation documents, appointing a registered agent, obtaining a Federal Employer Identification Number (EIN), registering for state payroll tax accounts, and configuring a compliant payroll system. Each step has hard dependencies on the one before it. Miss the sequencing, and you'll delay your first hire by a month or more.

Quick Facts: US Entity Setup for Foreign Companies

A US entity is a legally registered business structure formed under the laws of a US state that allows a foreign parent company to hire US employees directly, sign US contracts, and hold US bank and payroll tax accounts in the entity's name.

A practical EIN timeline for foreign-owned entities where the responsible party lacks a US SSN or ITIN is 4 business days by fax or 4-6 weeks by mail. EIN timing is the single most common critical path item that delays first payroll.

Total one-time costs to form a basic US entity and reach payroll readiness commonly land in the $1,500-$5,000+ range when combining state filing fees, registered agent, formation support, and initial payroll setup tasks.

New-employer State Unemployment Insurance (SUI) contribution rates commonly start around 2-4% of taxable wages in many states, with California new employers paying 3.4% for 2-3 years, and the taxable wage base is state-specific and resets annually.

Registered agent services for US entities typically cost $50-$300 per year, and a registered agent with a physical address in the state of formation is mandatory for most corporations and LLCs.

Should You Choose an EOR or Your Own US Entity?

Before diving into entity formation steps, you need to answer a fundamental question: is forming your own entity actually the right path for your situation right now?

An Employer of Record (EOR) differs from a US entity in speed because EOR onboarding is commonly achievable in days to 1-2 weeks, while entity formation plus payroll readiness commonly takes 6-10 weeks due to EIN and state payroll account dependencies. For companies hiring fewer than 10 employees or testing the US market, an EOR is typically faster and lower-risk.

Choose an EOR when you need a US hire to start in 1-2 weeks and you cannot accept the 6-10 week critical path created by EIN issuance, state tax registrations, and US banking setup. Choose your own US entity when you plan a sustained US presence and expect to scale beyond roughly 10 US employees, because fixed entity compliance costs typically amortise better at higher headcount than per-employee EOR fees.

The math tips toward entity formation when you're committed to a permanent US presence, hiring at scale, or preparing for a future acquisition. Teamed's graduation model helps companies navigate this decision by providing clear crossover economics: the calculation of when entity setup becomes cheaper than EOR based on your specific headcount and growth trajectory.

Step 1: Which Legal Structure Should You Choose for Your US Entity?

The three most common US entity structures for foreign companies are the C-Corporation, the LLC, and the S-Corporation. Most international companies choose the C-Corporation for its investor-friendliness and clean separation of foreign parent and US subsidiary, or the LLC for its tax flexibility and simpler administration.

A C-Corporation is the preferred structure for foreign-owned US subsidiaries when you anticipate institutional investment, a complex cap table, or an acquisition pathway that typically expects a corporate structure. C-Corps are taxed at the entity level, which creates potential double taxation on dividends but provides the clean cap table structure that US investors expect.

An LLC offers pass-through taxation and flexible internal allocation of profits and governance. However, single-member LLCs owned by foreign entities have specific IRS filing requirements, including Form 5472, which requires detailed reporting of transactions between the LLC and its foreign owner.

Here's a common mistake: S-Corporations are generally not available to foreign-owned entities due to ownership restrictions. S-Corps cannot have non-resident alien shareholders, which disqualifies most foreign parent companies. Don't waste time exploring this option if your parent company is based outside the US.

A US subsidiary is a separate US-incorporated company owned by a non-US parent company, designed to ring-fence US employment and contract liability from the parent while creating a clean structure for payroll, tax registrations, and US banking.

Step 2: Which State Should You Form Your US Entity In?

Foreign companies most commonly form their US entity in Delaware, Wyoming, or the state where they will primarily operate. Delaware is the default choice for companies seeking investment or planning an eventual IPO, with 81.4% of U.S.-based IPOs choosing Delaware as their corporate home due to its established corporate law and Court of Chancery.

Delaware offers a predictable legal framework, no state income tax on out-of-state revenue, and familiarity among US investors and legal counsel. The catch: if your employees work in California, Texas, or New York, you'll need to foreign-qualify in those states anyway, which adds cost and time.

A typical mid-market "Delaware formation plus foreign qualification where employees sit" approach adds a second set of state fees and an additional registration step, which commonly adds 1-4 weeks to the overall timeline depending on the operating state.

Wyoming offers low fees, strong LLC privacy protections, and no state income tax. It's a solid alternative for smaller operations that don't need Delaware's investor credibility.

Choose formation in the primary operating state when you will have an immediate physical office or a concentrated workforce in that state and you want to avoid the time and cost of foreign qualification. If you're hiring five people in California from day one, forming directly in California eliminates the dual-registration complexity.

Delaware filing fees run approximately $89 for corporations plus franchise taxes. California charges $800 minimum franchise tax annually regardless of revenue. Wyoming offers lower ongoing fees but less investor recognition.

Step 3: How Do You File Formation Documents and Appoint a Registered Agent?

To form a US entity, you must file Articles of Incorporation (for a Corporation) or Articles of Organization (for an LLC) with the Secretary of State in your chosen state. You must also designate a registered agent, a person or service with a physical US address authorised to receive legal documents on behalf of the company.

Articles of Incorporation typically include your company name, registered agent information, authorised shares, and incorporator details. The requirements are straightforward, but getting the details wrong can delay processing.

Commercial registered agent services like CT Corporation, Northwest Registered Agent, or Incfile handle this for $50-$300 per year. They provide a physical address in your formation state and forward legal documents to your team. For foreign-owned companies without a US presence, a commercial registered agent is essentially mandatory.

Timeline by state varies significantly. Delaware processes standard filings in 1-3 business days, with same-day expedited service available for additional fees. California takes 3-5 business days. Wyoming processes in 1-2 business days.

Foreign qualification filing is required if you form in Delaware but operate in a second state. This registration allows your Delaware entity to legally do business and employ staff in that operating state. Costs range from $100-$750 depending on the state, and processing times vary from same-day to several weeks.

Step 4: How Do You Obtain Your Federal Employer Identification Number (EIN)?

An Employer Identification Number (EIN) is a nine-digit federal tax ID issued by the IRS. It is required before you can open a US business bank account, hire employees, or register for state payroll tax accounts. This is the step that catches most international companies off guard.

If the responsible party has a US Social Security Number or ITIN, an EIN can be obtained online in minutes through the IRS website. The process is instant and free.

For foreign-owned entities where the responsible party lacks a US SSN, the IRS Form SS-4 must be submitted by fax (4 business days) or mail (4-6 weeks). Plan for the fax timeline as your baseline. The mail option should be avoided unless absolutely necessary.

Here's the critical sequencing note that most guides miss: state payroll tax accounts cannot be opened until the EIN is issued. This dependency is the most common cause of payroll delays for international companies. You cannot legally run payroll without a valid EIN, so factor EIN issuance time into your first hire's start date.

Teamed's implementation benchmarks show that EIN timing is consistently the single most common critical path item that delays first payroll for foreign-owned entities entering the US market.

Step 5: How Do You Register for State Payroll Tax Accounts?

After receiving your EIN, you must register for state payroll tax accounts in every state where you have employees. At minimum, this includes a State Income Tax Withholding account and a State Unemployment Insurance (SUI) account. Some states also require separate local tax registrations.

A State Withholding Account allows you to withhold and remit state income tax from employee wages. Registration is typically with the state Department of Revenue or Taxation. A State Unemployment Insurance (SUI) account funds state unemployment benefits and requires registration with the state Department of Labor or Workforce Commission.

Employee payroll taxes are based on the state where the employee works, not where the company is incorporated. A Delaware-incorporated company with an employee in California must register for California payroll taxes. This catches many international companies off guard, especially those with remote-first hiring strategies.

Registration timelines vary dramatically. California's Employment Development Department processes online registrations in 1-2 weeks. New York can take 2-4 weeks. Texas has no state income tax but still requires unemployment insurance registration. Florida similarly has no state income tax.

Local tax registrations add another layer of complexity in certain jurisdictions. Pennsylvania's Act 32 requires local earned income tax registration. Ohio uses RITA and CCA systems for municipal taxes. New York City, Philadelphia, and other high-compliance cities require separate registrations beyond state-level accounts.

If employees are in multiple states from day one, each state requires separate registration. Remote-first companies often underestimate this multi-state complexity significantly.

Step 6: How Do You Open a US Business Bank Account?

A US business bank account is required to fund payroll and pay federal and state tax deposits. Most major US banks require in-person account opening with original formation documents, EIN confirmation letter, and identification for all signatories, which creates a logistical challenge for foreign-based founders.

Traditional banks like Chase, Bank of America, and Silicon Valley Bank typically require an in-person visit to a US branch. You'll need original formation documents, your EIN confirmation letter, and identification for all account signatories. Some banks require minimum deposits or ongoing balance requirements.

Fintech alternatives have emerged specifically for foreign-owned entities. Mercury, Relay, and Brex offer remote account opening, faster setup, and no minimum balance requirements. These can significantly accelerate your timeline if in-person banking isn't feasible. Note that some fintech products may have different FDIC insurance structures than traditional bank accounts.

Open the account before payroll setup. Payroll providers require a verified US bank account for ACH direct deposit, and verification can take several days.

Step 7: How Do You Configure Your Payroll System and Run Your First Payroll?

Once your EIN, state tax accounts, and US bank account are in place, you can configure a US payroll system. Key decisions include pay frequency, payroll provider selection, and worker classification.

Biweekly pay is most common in the US, though some states mandate minimum pay frequency. California requires semi-monthly payment for most employees. Confirm state rules before setting your schedule.

Full-service payroll providers like Gusto, Rippling, ADP Run, and Paychex handle tax calculations, filings, and deposits automatically. For international companies navigating US payroll for the first time, full-service is strongly recommended over DIY approaches.

Before your first payroll run, you'll need to collect employee onboarding documents. Form W-4 captures federal withholding elections. State equivalent withholding forms vary by state. Form I-9 verifies employment eligibility and requires supporting documents. Direct deposit authorisation connects employee bank accounts.

Federal tax deposit schedules are determined by lookback period. New employers default to monthly depositor status in year one, meaning federal payroll taxes are due by the 15th of the following month.

Common first-year mistakes include misclassifying employees as independent contractors (1099 vs W-2), missing state SUI registration before first payroll run, using incorrect federal deposit schedules, and failing to register for local taxes in high-compliance cities.

What's the Full Timeline from Decision to First Payroll Run?

The complete journey from deciding to form a US entity to running your first compliant payroll typically takes 6-10 weeks. Here's how that breaks down.

Weeks 1-2 involve choosing your legal structure and state of formation. This decision-making phase requires input from legal and tax advisors but shouldn't take longer than two weeks with focused attention.

Weeks 2-3 cover filing formation documents and appointing your registered agent. Delaware processes in 1-3 business days; other states vary from same-day to one week.

Weeks 3-5 are consumed by EIN application. This is your critical path. Fax applications take 4 business days; mail applications take 4-6 weeks. Plan accordingly.

Weeks 5-7 involve registering for state payroll tax accounts. Timelines range from same-day online registration to 4 weeks depending on the state.

Weeks 6-8 cover opening your US business bank account. Allow 1-2 weeks for traditional banks; fintech options can be faster.

Weeks 8-10 are for configuring your payroll system and onboarding your first employee. Allow 1-2 weeks for setup, testing, and first payroll run.

Best case with expedited EIN processing: 4 weeks. Typical case for foreign-owned entities: 6-10 weeks.

Frequently Asked Questions

Which US state is best for forming an entity as a foreign company?

Delaware is the most common choice for foreign companies due to its established corporate law, investor familiarity, and Court of Chancery, with 66.7% of Fortune 500 companies incorporated there. Wyoming is a strong alternative for LLCs prioritising privacy and low fees. If your primary operations and workforce will be in a specific state like California or Texas, forming there directly avoids the cost and complexity of foreign qualification.

How long does it take to get an EIN as a foreign-owned company?

If the responsible party has a US Social Security Number or ITIN, an EIN can be obtained online in minutes. For foreign-owned entities where the responsible party lacks a US SSN, the IRS Form SS-4 must be submitted by fax (4 business days) or mail (4-6 weeks). Plan for the fax timeline as your baseline.

Can I run payroll before my EIN is issued?

No. A Federal Employer Identification Number is required to process payroll, open state tax accounts, and make federal tax deposits. You cannot legally run payroll without one. Factor EIN issuance time into your first hire's start date.

Do I need to register for payroll taxes in every state where I have employees?

Yes. Payroll tax obligations are based on where employees work, not where the company is incorporated. If you have employees in three states, you must register for withholding and unemployment insurance accounts in all three states, regardless of your state of formation.

What is the difference between a C-Corporation and an LLC for a foreign-owned US entity?

A C-Corporation is the preferred structure for foreign-owned subsidiaries seeking investment, planning an IPO, or wanting clean liability separation from the parent company. An LLC offers pass-through taxation and simpler administration but has specific IRS filing requirements for foreign-owned single-member LLCs (Form 5472). S-Corporations are generally not available to foreign-owned entities due to ownership restrictions.

How much does it cost to set up a US entity?

Total setup costs typically range from $1,500 to $5,000+ depending on state, legal structure, and whether you use an attorney. Key cost components include state filing fees ($50-$800), registered agent fees ($50-$300/year), EIN application (free via IRS), state payroll tax account registration (free to $200), and legal or formation service fees ($500-$3,000+).

Moving Forward with Your US Entity

Setting up a US entity as a foreign company requires navigating seven sequential steps with hard dependencies between them. The EIN-to-state-accounts sequencing is where most companies lose time, and multi-state payroll registration adds complexity that remote-first hiring strategies often underestimate.

The decision between EOR and entity formation isn't permanent. Many companies start with an EOR to move quickly, then graduate to their own entity when headcount and commitment justify the investment. Teamed's advisory approach helps companies navigate this transition, providing the right structure for where you are and trusted advice for where you're going.

If you're weighing the entity formation path against faster alternatives, or if you've already formed and need help with the payroll tax registration maze, talk to an expert who can map the sequencing to your specific timeline and hiring plans.

PEO Co-Employment vs EOR: What Actually Changes When You Sign

You've been down this road before. A vendor promised simplicity, and six months later you're untangling compliance issues nobody warned you about. Now you're comparing PEO co-employment against EOR full employer status, and every comparison article reads like it was written by someone selling one of them.

Here's what actually matters: these aren't two versions of the same thing. They're fundamentally different employment structures with different liability profiles, different geographic applications, and different implications for your business. The question isn't which vendor has better features. It's which legal relationship matches your situation.

Most mid-market companies operating across 2-15 countries discover this distinction the hard way. They choose based on cost or convenience, then learn that co-employment doesn't mean what they thought it meant, or that full employer status comes with trade-offs nobody mentioned. This guide breaks down the structural differences so you can make the decision with complete information.

What Changes Legally: PEO vs EOR

PEO co-employment creates a dual-employer relationship where both your company and the PEO share legal employer status, typically through a dual W-2 arrangement in the United States. EOR full employer status makes the provider the sole legal employer, with your company directing work through a commercial services agreement rather than an employment contract. PEO arrangements generally require your company to have an existing legal entity in the jurisdiction where workers are located. EOR arrangements are specifically designed for hiring in countries where you have no local entity, enabling market entry without incorporation. Co-employment splits employer liability between both parties, while EOR consolidates all local employment compliance under a single legal employer. PEO services operate primarily in the United States, while EOR services cover 187+ countries globally. Teamed's analysis across 1,000+ companies shows the right choice depends on geography, control requirements, and risk tolerance rather than cost alone.

What Is Co-Employment in a PEO Arrangement?

Co-employment is an employment structure in which your company and a Professional Employer Organization both hold employer responsibilities for the same workers. Your company retains day-to-day direction of work, performance management, and workplace decisions. The PEO typically administers payroll, benefits, tax filings, and HR compliance functions.

The defining feature is shared employer status. Both parties appear on the W-2. Both parties carry employer liability. This isn't a technicality buried in contract language. It's the fundamental legal architecture of the relationship.

What does the PEO actually own? Payroll processing, tax withholding and filing, benefits administration, and workers' compensation coverage. The PEO pools purchasing power across its client base, which often means access to Fortune 500-level benefits at SMB pricing. They handle the administrative machinery of employment, which represents 29.7% of total compensation for U.S. private-industry employers.

What do you retain? Everything related to actually managing your workforce. Hiring decisions, work assignments, performance reviews, discipline, and termination decisions remain with you. The PEO executes the paperwork, but you make the calls.

The misconception worth correcting: co-employment does not mean loss of control over your workforce. You're not handing management authority to the PEO. You're outsourcing administrative functions while remaining an employer with ongoing workplace obligations.

What Is Full Employer Status in an EOR Arrangement?

An Employer of Record is a third-party organisation that becomes the sole legal employer for a worker in a specific country through its local entity. The EOR holds the employment contract, runs local payroll, withholds taxes, registers for employer social security, and manages all statutory employment obligations.

Your company directs the worker's tasks under a commercial services agreement, not an employment contract. The worker operates as part of your team day-to-day, but the legal employment relationship exists between the worker and the EOR.

The critical distinction: you have no direct employment relationship with the worker in their country. This matters enormously for liability, compliance, and how employment actions must be executed.

What does the EOR own? The employment contract, payroll and tax filings, statutory benefits administration, termination execution, and all in-country compliance obligations. When something goes wrong with local labour law, the EOR is the accountable party.

What do you retain? Direction of work, project assignments, team integration, and performance feedback. You manage the work. The EOR manages the employment.

The misconception worth correcting: full employer status doesn't mean the EOR makes HR decisions for you. You still decide who to hire, what they work on, and when the relationship should end. The EOR executes those decisions through proper local channels.

How Does PEO Co-Employment Differ from EOR Full Employer Status?

The structural differences between these models affect every aspect of how you operate internationally. Understanding these distinctions prevents expensive surprises.

Who's the employer on paper? That's what separates these models.

In PEO co-employment, both your company and the PEO are recognised as employers with shared obligations. In EOR arrangements, the EOR alone holds legal employer status in the worker's country. This single difference cascades through every other consideration.

Entity requirements follow directly from employer status. PEO arrangements presume you already have an employing entity in the jurisdiction. You can't enter a co-employment relationship in a country where you don't legally exist. EOR arrangements are purpose-built for the opposite scenario, employing workers through the provider's local entity when you have no presence.

Liability distribution reflects the employer status split. Co-employment shares compliance responsibility across two employers, which sounds like reduced risk until you realise you remain liable for workplace decisions, discrimination claims, and termination disputes. EOR consolidates local employment compliance execution under a single legal employer, though permanent establishment risk can still attribute employer status to you under certain conditions.

Termination mechanics differ significantly. Under co-employment, you typically lead performance management and termination decisions, with the PEO handling administrative execution. Under EOR, formal termination must be executed by the EOR as the legal employer, following local procedural requirements you may not control directly.

Geographic scope determines practical applicability. PEO services operate primarily in the United States, with some providers offering limited international coverage. EOR services are designed specifically for cross-border hiring, covering 187+ countries through networks of local entities.

What Are the Advantages of PEO Co-Employment?

PEO makes sense when you already have a US entity and want someone else to handle the HR admin while you stay the employer.

Access to pooled benefits purchasing power often represents the most tangible advantage. A 75-person company can offer health insurance, retirement plans, and supplemental benefits at rates typically available only to much larger organisations, significant when family coverage now averages $26,993 annually. The PEO aggregates thousands of employees across its client base, negotiating group rates that individual mid-market companies can't access independently.

Reduced administrative burden follows naturally. Payroll processing, tax filings, benefits enrolment, and HR compliance documentation shift to the PEO. Your internal team focuses on strategic HR work rather than processing paperwork. For companies scaling rapidly across multiple US states, this consolidation prevents compliance from fragmenting across dozens of state-specific requirements.

Shared employer liability lowers your solo exposure on benefits and payroll compliance. The PEO assumes EPLI (Employment Practices Liability Insurance) exposure in many arrangements, providing coverage for claims that might otherwise hit your balance sheet directly. When payroll taxes are filed incorrectly, the PEO shares accountability.

Faster onboarding for domestic hires becomes possible because the infrastructure already exists. New employees slot into established payroll, benefits, and compliance systems without requiring you to build internal HR infrastructure from scratch.

What Are the Disadvantages of PEO Co-Employment?

Co-employment creates dual liability, and that's not the same as reduced liability. You remain a legal employer with exposure for workplace decisions, discrimination claims, wrongful termination suits, and safety violations. The PEO absorbs payroll and benefits compliance risk, but not all HR risk. When an employee sues over a termination decision you made, co-employment doesn't shield you.

Entity requirements limit applicability. PEO arrangements require you to have an existing legal entity in the jurisdiction. A UK company wanting to hire in the United States must first establish a US entity before engaging a PEO. For companies testing new markets, this creates a chicken-and-egg problem.

Geographic limitations constrain international use. Most PEOs operate exclusively in the United States. A few offer limited international coverage, but the co-employment model doesn't translate cleanly to jurisdictions with different employment law frameworks. For global hiring, PEO simply isn't the tool.

Contract stickiness complicates transitions. Transitioning employees off a PEO mid-growth requires planning. Benefits continuity, payroll cutover, and administrative handoffs create friction. Companies that outgrow their PEO arrangement often face more complexity exiting than they anticipated entering.

Flexibility limitations affect non-standard arrangements. Contractors, project-based workers, and variable-hour employees don't fit neatly into co-employment structures designed for traditional full-time employment.

What Are the Advantages of EOR Full Employer Status?

EOR full employer status eliminates direct employment liability in the worker's country. The EOR holds the employment contract and bears accountability for local compliance. When French labour law requires specific termination procedures, the EOR executes them. When German works council requirements apply, the EOR navigates them.

No local entity requirement enables immediate market entry. You can hire your first employee in Singapore, Brazil, or Poland without establishing a legal presence. Entity formation typically requires 2-6 months and significant legal and administrative investment. EOR bypasses that entirely, with onboarding possible in as little as 24 hours when required information is available.

Global hiring capability is built into the model. EOR providers maintain local entities across dozens or hundreds of countries specifically to employ workers on behalf of clients. Teamed operates EOR services covering 187+ countries, enabling UK and EU mid-market companies to hire without geographic constraints.

Clean contractual separation governs the relationship. Your connection to the worker flows through a services agreement, not an employment contract. This distinction matters for corporate structure, liability allocation, and how the relationship appears to tax authorities.

Market testing becomes practical. Before committing to entity establishment, you can validate product-market fit, assess talent availability, and confirm long-term viability through EOR. If the market doesn't develop as expected, exit is straightforward.

What Are the Disadvantages of EOR Full Employer Status?

Higher per-employee cost reflects the liability absorption. Full employer status means the EOR carries compliance risk, termination liability, and administrative burden. That's priced accordingly. Teamed's published headline EOR fee is $599 per employee per month with zero FX markup, but EOR will always cost more than PEO on a per-head basis because it delivers more.

Reduced direct HR authority requires adjustment. All formal employment actions must route through the EOR as legal employer. You can't issue a termination letter directly. Contract amendments require EOR execution. This adds process steps that companies accustomed to direct employment find unfamiliar.

EOR model recognition varies by jurisdiction. Not every country's legal framework accommodates EOR arrangements cleanly. Some jurisdictions view EOR as labour leasing with specific restrictions. In Germany, employee leasing (Arbeitnehmerüberlassung) rules can apply to labour-supply models, restricting assignment length to 18 months maximum and creating equal-pay obligations.

Permanent establishment risk persists despite EOR. If EOR workers are deeply integrated into client operations, particularly if they have contract-signing authority, generate revenue, or make management decisions, tax authorities may still attribute employer status to you. EOR reduces but doesn't eliminate PE exposure.

Scale economics favour entity formation eventually. For large, stable domestic workforces, direct employment or PEO becomes more cost-efficient than EOR. The crossover point varies by country complexity, but every EOR customer eventually reaches a threshold where entity ownership makes economic sense.

When Should You Choose PEO Co-Employment?

Choose a PEO co-employment model when your workers will be employed by your existing local entity and you mainly want administrative relief rather than a transfer of legal employer status.

The clearest PEO use case is a US-based company with 10-150 employees wanting to offload HR administration without losing workforce control. You have the entity. You want to remain an employer. You need help with the paperwork.

Companies scaling headcount rapidly across multiple US states benefit from PEO's multi-state compliance coverage. Rather than tracking registration requirements, tax rates, and employment law variations across 30+ states with different minimum wages, the PEO consolidates that complexity.

SMBs that cannot self-fund competitive benefits packages need PEO pooling to attract talent. When you're competing for candidates against companies offering better health insurance and retirement plans, PEO purchasing power levels the playing field.

Organisations wanting shared rather than transferred employer liability fit the co-employment model. You're not trying to eliminate your employer status. You're trying to share the administrative and compliance burden with a partner.

When Should You Choose EOR Full Employer Status?

Choose an EOR when you need to hire in a country where you have no local entity and you want to eliminate direct employment liability for that worker population.

The clearest EOR use case is hiring your first employee in a foreign country without establishing a local presence. You've identified talent in the Netherlands, but you have no Dutch entity. EOR solves that problem immediately.

Companies testing new international markets before committing to permanent establishment benefit from EOR's flexibility. Entity formation in Germany requires 4-6 months and significant investment. EOR lets you hire, validate the market, and make the entity decision with actual data.

Organisations wanting to eliminate direct employment liability entirely for specific worker populations find EOR appropriate. When your legal team requires one party to hold the employment contract locally and be accountable for in-country compliance, EOR delivers that structure.

Contractor-to-employee conversions in jurisdictions with strict misclassification enforcement often require EOR. When a contractor relationship has evolved to look like employment, with fixed hours, ongoing direction, and team integration, converting to EOR employment eliminates misclassification exposure.

How Do You Decide Between PEO and EOR?

The decision framework is simpler than most comparison articles suggest. Geography and entity status determine the answer in most cases.

If your workforce is primarily domestic (US) and you have an existing legal entity and you want to retain HR control, PEO co-employment is likely the better fit. You're not trying to solve a cross-border problem. You're trying to solve an administrative efficiency problem.

If you're hiring outside your home country and you don't have a local entity and you want to eliminate direct employment liability, EOR full employer status is likely the better fit. You're solving a market access problem that PEO can't address.

If you're scaling both domestically and internationally, consider a PEO for domestic headcount plus EOR for international hires. Many providers support both models, and the combination matches different needs in different markets.

If your primary concern is cost efficiency at scale with 50+ domestic employees, PEO typically delivers better unit economics than EOR. The administrative relief comes at lower per-head cost than full liability transfer.

If your primary concern is speed to hire in a new country, EOR wins on time-to-hire and compliance certainty. Entity formation takes months. EOR takes days.

What Happens When You Outgrow Either Model?

Every employment model has a crossover point. For PEO, it's when you've grown large enough that bringing HR administration in-house makes economic sense. For EOR, it's when headcount concentration in a single country justifies entity establishment.

Teamed's graduation model addresses this reality directly. Companies progress naturally from contractors to EOR to owned entities as they scale. The question isn't whether you'll transition. It's when the economics and operational requirements make transition appropriate.

For EOR specifically, the crossover varies by country complexity. Low-complexity countries like the United Kingdom, Ireland, and Singapore justify entity setup at 10+ employees. High-complexity countries like Brazil, India, and China may warrant staying on EOR until 25-35 employees. The calculation involves entity setup costs, ongoing administration costs, and the compliance burden you're prepared to absorb.

The right provider proactively advises when it's time to move to the next stage, even when that means moving you off their higher-margin product. Teamed states it's the only EOR provider that proactively tells you when to stop using EOR and graduate to your own entity. That's not altruism. It's recognition that graduation is revenue expansion, not churn, when you maintain the relationship through the transition.

What Are the Main Risks of Co-Employment in a PEO?

The primary risk is misunderstanding what co-employment actually means. Co-employment does not eliminate client-side employer liability. You remain a legal employer with exposure for workplace decisions, discrimination claims, and wrongful termination suits. The PEO absorbs payroll and benefits compliance risk, but not all HR risk.

Joint employer liability creates complexity when things go wrong. If an employee brings a claim, both you and the PEO may be named. Determining which party bears responsibility for which aspect of the claim requires careful analysis of the co-employment agreement and the specific facts.

Regulatory scrutiny of co-employment arrangements has increased. Some jurisdictions view co-employment structures skeptically, particularly when the arrangement appears designed to avoid employer obligations rather than achieve legitimate administrative efficiency.

Exit complexity catches companies unprepared. When you leave a PEO, employees transition to direct employment with your company. You must establish your own payroll, benefits, and HR infrastructure to absorb those workers. Abrupt exits disrupt benefits continuity and create administrative chaos.

Can a PEO Replace an EOR for International Hiring?

Generally, no. Most PEOs operate exclusively in the United States and require the client to have a domestic legal entity. EORs are purpose-built for cross-border hiring and don't require you to establish a local entity in the worker's country.

The models solve different problems. PEO solves "I have employees and need help administering their employment." EOR solves "I need to employ someone in a country where I have no legal presence."

A few providers market international PEO services, but these typically involve different structures than domestic US co-employment. The terminology can be confusing. When evaluating international options, focus on the underlying legal structure rather than the marketing label.

For mid-market companies operating across multiple countries, the practical reality is that EOR handles international hiring while PEO handles domestic administration. Trying to force PEO into international use cases creates compliance exposure and operational friction.

Making the Right Structural Decision

The PEO versus EOR decision isn't about finding the better vendor. It's about matching employment structure to your actual situation. Geography, entity status, liability preferences, and growth trajectory determine the right answer.

Most mid-market companies need both models at different points in their evolution. Domestic operations benefit from PEO's administrative efficiency. International expansion requires EOR's market access capability. The companies that navigate this well treat employment structure as a strategic decision rather than a vendor selection exercise.

Teamed works with mid-market companies across this entire spectrum, from first international hire through entity establishment and beyond. If you're evaluating which structure fits your current situation and where you're headed, talk to an expert who can assess your specific circumstances rather than selling you a predetermined answer.

How an EOR Keeps You Compliant with Malaysia's Employment Act — Including the 2026 Updates

Malaysia's Employment Act 1955 creates a dense web of employer obligations that catches foreign companies off guard. The Act covers all employees earning MYR 4,000 per month or less automatically, plus manual workers regardless of salary. Miss a statutory deadline, miscalculate an EPF contribution, or fail to update your contracts for the 2026 amendments, and you're facing Labour Department fines, back-pay liability, and reputational damage that's hard to undo.

An Employer of Record in Malaysia assumes legal employer status, which means it holds the Employment Act obligations rather than your company. The EOR registers with EPF (KWSP), SOCSO (PERKESO), and EIS, processes PCB/MTD tax withholding, issues EA-compliant contracts, and absorbs regulatory updates like the 2026 amendments into its payroll and HR systems before the effective date. Your company directs the employee's day-to-day work but carries no direct employment law liability.

This article maps each major Employment Act provision and 2026 update to the specific EOR workflow that handles it. You'll understand the operational mechanism, not just the rules, and walk away with a responsibility matrix showing exactly who owns what when you hire through an EOR in Malaysia.

Quick Facts: Malaysia Employment Act Compliance Through an EOR

Malaysia's statutory maximum working hours under the Employment Act are 45 hours per week, requiring EOR payroll systems to flag schedules exceeding this threshold before finalisation.

EPF employer contributions are 13% for employees earning MYR 5,000 or below and 12% above that threshold, with employee contributions at 11%.

EIS contributions are 0.4% from employer plus 0.4% from employee, calculated only up to a MYR 4,000 wage ceiling.

The statutory minimum maternity leave entitlement is 98 days under the Employment Act's 2022 amendments.

Annual leave entitlements range from 8 to 16 days depending on years of service, with sick leave ranging from 14 to 22 days.

Teamed's EOR fee is USD 599 per employee per month with zero FX markup contractually guaranteed, allowing Finance teams to separate provider costs from statutory obligations.

What Is an Employer of Record Under Malaysian Law?

An Employer of Record is a third-party entity that legally employs workers in Malaysia on behalf of a foreign or domestic client company. The EOR's local legal entity, typically a Sdn. Bhd., signs the employment contract, registers the employee with statutory bodies including EPF, SOCSO, and EIS, withholds and remits PCB/MTD tax to LHDN, and is the named employer under the Employment Act 1955.

The client company directs the employee's day-to-day work, approves leave requests, and makes business decisions about roles and compensation. But the EOR holds the legal employment relationship. When the Labour Department investigates a complaint or conducts an audit, the EOR is the entity on the hook for potential wrongful termination claims, not your company.

This structure differs from a Professional Employer Organization model, where the client typically already has a local employing entity. It also differs from contractor arrangements, where statutory contributions like EPF and SOCSO aren't processed through payroll in the same way, shifting risk from payroll compliance to classification compliance.

What Does the Malaysia Employment Act Actually Require of Employers?

Who Falls Under Employment Act Coverage?

According to JTKSM's official guidance, all private-sector employees are covered by the Employment Act regardless of salary, though employees earning more than MYR 4,000 per month (except manual workers) are not entitled to overtime pay, rest-day/public-holiday pay, or termination benefits. Manual workers are covered regardless of salary. The 2022 amendments expanded coverage significantly, and the 2026 updates build on this foundation.

A pay threshold alone doesn't remove Employment Act obligations. If your Malaysia hire earns MYR 5,000 monthly but performs manual work, they're still covered. The EOR's contract templates and payroll configurations must account for this nuance, which is exactly the kind of edge case that trips up companies managing compliance manually.

Key obligations triggered by Employment Act coverage include written contracts, maximum 45-hour working weeks, overtime rates at 1.5x for normal days, annual and sick leave minimums, maternity leave at 98 days, and termination notice periods based on tenure.

How Do EPF, SOCSO, and EIS Contributions Work?

EPF (Employees Provident Fund) requires employer contributions of 13% for employees earning MYR 5,000 or below, dropping to 12% above that threshold. Employees contribute 11%. The EOR registers each employee under its employer number and remits both sides monthly.

SOCSO (Social Security Organisation) covers work injury and invalidity. Contribution rates vary by salary band, with both employer and employee portions calculated according to prescribed tables. The EOR handles registration and remittance under its PERKESO account.

EIS (Employment Insurance System) provides unemployment coverage. According to PERKESO's current guidance, contributions are 0.2% from employer plus 0.2% from employee, calculated up to a MYR 6,000 wage ceiling. Even if monthly salary exceeds MYR 4,000, the EOR must cap EIS calculations at that ceiling.

PCB/MTD (Monthly Tax Deduction) requires the employer to calculate, deduct, and remit employee income tax instalments to LHDN by the 15th day of the following month, with non-compliance potentially triggering fines of MYR 200 to MYR 20,000. The EOR's payroll engine handles this automatically, issuing EA forms annually.

What Are the Leave and Termination Entitlements?

Annual leave entitlements under the Employment Act scale with service length. Employees with less than two years receive 8 days, those with two to five years receive 12 days, and those with more than five years receive 16 days. The EOR's HR system tracks balances against these statutory minimums.

Sick leave follows a similar pattern. Employees receive 14 days for less than two years of service, 18 days for two to five years, and 22 days for more than five years. Hospitalisation adds up to 60 days annually.

Maternity leave is 98 days under the 2022 amendments, a significant increase from the previous 60 days. The EOR must ensure payroll and leave systems can process a 98-day maternity absence without breaking statutory minimums.

Termination requires notice periods based on tenure, and retrenchment benefits under the Employment (Termination and Lay-Off Benefits) Regulations 1980 may apply. The EOR manages notice period calculations, final pay including accrued leave encashment, and statutory deregistration.

How Does an EOR Handle the 2026 Malaysia Labour Law Updates?

The 2026 amendments build on the 2022 Employment Act overhaul and introduce changes that directly affect how employers structure work arrangements, calculate overtime, and handle flexible work requests. Most competitor content lists these changes without explaining how an EOR actually implements them. Here's the operational reality.

What Changed with Flexible Work Arrangement Rights?

Employees now have a statutory right to formally request flexible work arrangements covering hours, days, or location. Employers must respond within 60 days with written reasons if refusing the request.

The EOR handles this by updating employment contract templates to include the FWA request procedure. The EOR maintains a documented response workflow, ensuring refusals are logged with compliant written reasoning. This protects your company from Labour Department disputes over procedural failures.

When an employee submits an FWA request, the EOR routes it to you for the business decision. You decide whether to approve or refuse and provide the business reason. The EOR documents everything and ensures the response meets the 60-day deadline with proper written justification.

How Does the Overtime Eligibility Threshold Adjustment Affect Payroll?

The 2026 amendments revised the salary threshold for mandatory overtime pay eligibility upward, bringing more white-collar employees into OT entitlement scope. This means employees who previously weren't entitled to overtime pay may now qualify.

The EOR's payroll engine is reconfigured before the effective date to apply the new threshold. Affected employees' contracts are amended with updated OT clauses. Your company receives notification of any cost impact before the change takes effect, giving Finance teams time to adjust budgets.

This is exactly the kind of mid-year regulatory change that creates compliance gaps for companies managing Malaysia employment directly. The EOR absorbs the implementation burden, and you see the impact in your next payroll summary.

What Are the Enhanced Protections Against Constructive Dismissal?

Stronger statutory language around constructive dismissal makes it easier for employees to claim unfair termination if working conditions are materially changed without consent. Role changes, compensation adjustments, or location transfers that the employee didn't agree to can now trigger claims more easily.

The EOR's HR team reviews any proposed role, compensation, or location changes against the new standard before implementation. The EOR acts as a buffer between your business decisions and legally risky unilateral changes. If you want to modify an employee's terms, the EOR advises on whether consent is required and documents the process properly.

How Is Paternity Leave Now Codified?

Paternity leave entitlement is now codified in statute with a minimum of 7 days for private sector employees. Previously, this was discretionary or contractual.

The EOR updates contract templates automatically. Payroll is configured to process paternity leave pay correctly. No action required from your company. The compliance mechanics are invisible to you, but the statutory obligation is fully met.

How Does an EOR Manage Malaysia Employment Act Compliance Step by Step?

Most cited sources treat EOR compliance as a checklist of statutory obligations without explaining the operational mechanism. Here's the actual workflow that executes each requirement.

Step 1: Legal Entity Setup and Statutory Registration. The EOR's Malaysian legal entity registers as an employer with EPF (KWSP), SOCSO (PERKESO), EIS, and LHDN before the first employee is onboarded. Your company doesn't need a local entity. The EOR's existing registrations are used immediately.

Step 2: Employment Contract Drafting. The EOR issues an Employment Act-compliant contract in the employee's name, covering all mandatory terms including salary, working hours, leave entitlements, notice periods, and FWA request procedures. Contracts are versioned when the law changes, ensuring every employee has current terms.

Step 3: Payroll Processing and Statutory Contributions. Each payroll cycle, the EOR calculates gross pay, deducts employee-side EPF, SOCSO, EIS, and PCB, adds employer-side contributions, and remits all amounts to the respective statutory bodies by legal deadlines. You receive a payroll summary. The compliance mechanics are invisible.

Step 4: Leave Management and Entitlement Tracking. The EOR's HR system tracks each employee's leave balances against EA-mandated minimums, flags when entitlements are approaching statutory thresholds, and ensures leave encashment or carry-over is handled per the Act.

Step 5: Ongoing Regulatory Monitoring. The EOR's in-country legal and compliance team monitors Gazette notifications, Labour Department circulars, and court decisions affecting Employment Act interpretation. When a change is confirmed, the EOR updates contracts, payroll configurations, and HR policies before the effective date.

Step 6: Termination and Offboarding. When employment ends, the EOR manages notice period calculations, final pay including accrued leave encashment, EPF/SOCSO/EIS deregistration, and retrenchment benefit calculations where applicable. Your company is shielded from direct Labour Department exposure.

Who Is Responsible for What When Using an EOR in Malaysia?

This is the question procurement and legal teams ask most frequently, yet no competitor content provides a clear answer. Here's the responsibility split as of 2026.

Employment contract issuance: The EOR drafts, issues, and updates EA-compliant contracts. Your company approves role scope, salary, and start date.

EPF registration and contributions: The EOR registers employees and calculates and remits employer plus employee EPF. Your company has no direct responsibility.

SOCSO and EIS contributions: The EOR handles registration and remittance for both. Your company has no direct responsibility.

PCB/MTD tax withholding: The EOR withholds and remits monthly to LHDN and issues EA forms annually. Your company provides accurate expense and benefit data if applicable.

Overtime calculation and payment: The EOR applies correct OT rates per EA and 2026 thresholds. Your company approves and logs OT hours worked.

Annual, sick, maternity, and paternity leave: The EOR tracks entitlements, processes leave pay, and ensures EA minimums. Your company approves leave requests and communicates to the EOR.

Flexible work arrangement requests: The EOR maintains compliant FWA response workflow and documents decisions. Your company decides whether to approve or refuse and provides business reasons.

Termination and retrenchment: The EOR manages notice, final pay, statutory deregistration, and retrenchment benefits. Your company makes the business decision to terminate and provides the reason.

Regulatory update implementation: The EOR monitors, interprets, and implements all EA changes. Your company receives notification of changes and cost impact.

What Should You Look for in an EOR's Malaysia Compliance Infrastructure?

When evaluating EOR providers for Malaysia, the strength of compliance is only as good as the local legal infrastructure. Here's what to verify.

Confirm the EOR has its own Malaysian-registered entity, typically a Sdn. Bhd., rather than a sub-contractor arrangement. Sub-contracting creates compliance gaps where the named employer on paper isn't the entity actually managing statutory obligations.

Ask for proof of active EPF, SOCSO, EIS, and LHDN employer registration numbers. These should be in the EOR's own name, not a third party's.

Understand the contract versioning process. How quickly does the EOR update employment contracts when the law changes? What was their response time to the 2022 amendments? The 2026 updates require similar agility.

Verify 2026 update readiness. Has the EOR already updated its payroll engine and contract templates for the 2026 changes? Get confirmation in writing. If they're still "working on it" after the effective date, that's a red flag.

Clarify Labour Department dispute handling. Does the EOR represent the employer in Labour Court proceedings, or does liability revert to your company? The answer should be unambiguous.

Teamed's analysis of mid-market companies expanding into Malaysia shows that the most common compliance failures occur during regulatory transitions, exactly when an EOR's implementation speed matters most. Based on Teamed's work with companies across APAC, the providers who struggle are those using third-party reseller models rather than owning their local entities directly.

When Does EOR Make Sense Versus Your Own Malaysia Entity?

Choose an EOR in Malaysia when you need to hire in-country without setting up a Malaysian Sdn. Bhd. and you want the EOR to be the legal employer responsible for Employment Act minimum standards and statutory remittances. This is the right structure when you're testing the market, hiring your first few employees, or when headcount doesn't justify entity setup costs.

Choose your own Malaysia entity when you expect sustained headcount growth and want direct employer control over policies, benefits design, and IP or employee incentive structures that may be constrained by an EOR's standardised employment framework. The crossover point typically occurs at 15-20 employees in Malaysia, depending on your specific situation and cost of compliance considerations.

Teamed's Graduation Model provides a framework for this decision. Companies start with EOR when compliance requirements are complex but headcount is low. As the team grows, Teamed proactively advises when entity establishment becomes the better structure economically and operationally, managing the transfer from EOR to direct employment. The relationship continues through the transition, avoiding the re-onboarding and vendor switching that fragmented approaches require.

For mid-market companies operating across multiple APAC countries, the right structure for where you are matters more than locking into one model indefinitely. Malaysia's moderate complexity, with its multi-layered statutory contribution system and frequent regulatory updates, makes it a jurisdiction where EOR often remains the right answer longer than companies expect, though it doesn't rank among the most complex countries to run payroll.

Moving Forward with Malaysia Employment Compliance

An EOR ensures Malaysia Employment Act compliance by becoming the legal employer, absorbing all statutory obligations, and operationalising regulatory changes before they affect your company. The 2026 updates on flexible work arrangements, overtime eligibility, constructive dismissal protections, and paternity leave are already implemented in a properly structured EOR relationship.

For companies hiring in Malaysia without a local entity, or those currently managing compliance manually across multiple vendors, an EOR removes the execution risk entirely. The compliance value isn't just knowing the rules. It's owning the operational steps that execute them, from registration to offboarding, with no compliance gaps between regulatory updates.

If you're evaluating EOR providers for Malaysia or questioning whether your current structure is still the right one, talk to an expert about your specific situation. The honest answer about what structure fits your needs, even when that means advising you to change, is the service.

Ireland just missed the 7 June 2026 Pay Transparency deadline. Here's what actually changes for employers.

Ireland has confirmed it will miss the 7 June 2026 EU Pay Transparency Directive deadline. Irish employers face no penalties in the interim period because the national law has not yet been enacted. The European Commission can open infringement proceedings against Ireland as a state, but no action against individual employers is expected before domestic legislation is in place.

Group reporting frameworks that treat the EU as a single compliance bloc are now provably wrong for any employer with Irish staff. The Irish Times reported on 23 April 2026 that the Irish government will not transpose Directive 2023/970 into national law by the deadline. Ireland becomes the first member state to publicly acknowledge a missed transposition.

If you've been building your pay transparency programme around a single 7 June go-live date across all EU countries, you now have a problem to unpick. The picture is fragmenting in public. Netherlands is already live. France and Germany are on track. Malta has formally requested a postponement. And Ireland? Outside the reporting framework for an undefined period.

What actually changes today

Ireland will not transpose the EU Pay Transparency Directive by the 7 June 2026 deadline, as confirmed by The Irish Times on 23 April 2026.

No Irish law means no Irish fines. There's nothing on the Irish statute books to enforce against you yet.

Under Article 34 of the Directive, the Commission can pursue Ireland as a country. It can't pursue your business.

The Netherlands' pay transparency implementing bill is expected to enter into force on 1 January 2027. That alone means different EU countries are switching on at different times, and your reporting needs to reflect that.

Irish equal pay law still bites. The Employment Equality Acts haven't gone anywhere, and employees can still rely on them. In fact, employers with 50+ staff already have mandatory gender pay gap reporting obligations under existing Irish law.

Using an EOR in Ireland doesn't shift the timeline. Irish law applies whether your people are on your payroll or ours.

No new date has been set. Late 2026 is a reasonable working assumption, but nobody in Dublin has committed to one yet.

What has Ireland confirmed?

On 23 April 2026, The Irish Times reported that the Irish government will not transpose the EU Pay Transparency Directive into national law by the 7 June 2026 deadline. Ireland is the first EU member state to publicly acknowledge a missed transposition. The government cited drafting and consultation delays as the primary reasons.

This confirmation matters because it breaks the assumption that 7 June 2026 represents a single pan-EU compliance date. Pay transparency becomes enforceable on a country-by-country basis at national entry-into-force, not on the Directive deadline date. For any employer operating across multiple EU jurisdictions, this distinction is critical to accurate compliance planning.

The Irish government has signalled that implementation will proceed on a phased basis. No formal alternative date has been set, leaving HR and legal teams without a clear target for Irish-specific readiness.

Why will Ireland miss the deadline?

The Irish government cited drafting and consultation delays as the reasons for missing the 7 June 2026 deadline. The legislative process required to transpose EU directives into Irish law involves multiple stages of drafting, stakeholder consultation, and parliamentary approval. These stages have not been completed in time.

Ireland's transposition process requires national legislation to create local enforcement mechanisms, define offences, establish penalties, and designate enforcement bodies. Without this domestic legal framework, the Directive cannot operate as a fully enforceable employer compliance regime in Ireland. The complexity of translating EU minimum standards into Irish-specific procedures has extended the timeline beyond the three-year transposition period.

No draft Irish transposition bill has been published as of late April 2026. The implementation timeline remains unclear, with most observers expecting Q3 or Q4 2026 at the earliest for any substantive legislation to emerge.

What happens to Irish employers in the interim?

Irish employers face no penalties during the interim period. Here's why: without enacted national legislation, there is no legal mechanism through which to enforce Directive 2023/970 obligations or impose fines on employers. The Directive creates EU-level minimum standards, but employers are only directly subject to enforceable obligations when national implementing legislation is enacted and in force.

This creates a gap between the EU deadline and actual employer compliance requirements in Ireland. Your Irish payroll cannot be treated as "live" under Directive 2023/970 until national legislation is enacted. The transparency rights, pay reporting obligations, and access to remedies established by the Directive do not become operational for Irish employers until Ireland completes its transposition.

That said, this doesn't mean Irish employees have no protections. Existing Irish equal pay law continues to apply. The Employment Equality Acts provide baseline equal pay protections that remain in force regardless of Directive transposition status. Employees can still bring equal pay claims under existing Irish equality framework provisions. The Workplace Relations Commission received 14,890 complaints in 2024, with 27% relating to pay issues.

Where does the European Commission come in?

The European Commission retains the power to open infringement proceedings against Ireland as a member state. This is explicitly provided for in Directive 2023/970 Article 34, which addresses enforcement at member state level. Infringement proceedings target Ireland's failure to transpose EU law, not individual Irish employers.

Infringement proceedings differ fundamentally from employer penalties. The Commission's action would be directed at Ireland as a state through a formal enforcement process that can ultimately be referred to the Court of Justice of the European Union. This process does not create a direct EU fine mechanism for employers. Individual employer penalties require a domestic legal basis defining offences, enforcement powers, and fine levels.

For practical purposes, no action against individual Irish employers is expected in the interim period. The Commission's enforcement tools address state-level compliance failures, not employer-level obligations that don't yet exist in Irish law.

What this does to your EU-wide reporting

Group reports that treat the EU as a single compliance bloc are now demonstrably wrong for any employer with Irish staff. A multi-country employer with Irish and Dutch staff must treat pay transparency as a staggered compliance rollout rather than a single 7 June 2026 switch.

The Netherlands was reported as already live with pay transparency-related changes from April 2026. France and Germany are on track for June implementation. Malta has formally requested a postponement. Latvia, Czech Republic, Slovakia, and Romania have national transpositions with deviations from the Directive text. Each country's obligations become employer-enforceable only when that country's national implementing law enters into force.

Your reporting framework needs a jurisdiction-by-jurisdiction split. Teamed's analysis of multi-country compliance programmes shows that the fastest route to credible pay reporting is a single job and level framework mapped to each local payroll code. This mapping step typically takes 2-4 weeks for a 200-2,000 employee organisation operating in 3-8 countries. Without this foundation, you'll struggle to produce comparable pay gap metrics across jurisdictions with different go-live dates.

Separate your Irish reporting from live-jurisdiction reporting. Label each country clearly as live, pending, or deviating from Directive 2023/970 requirements. This prevents compliance confusion and ensures your board and employees receive accurate information about where obligations actually apply.

Where does this leave Irish employees?

Irish employees' baseline equal pay protections continue to arise under Ireland's existing equality framework. The Employment Equality Acts provide protections against pay discrimination that remain in force regardless of Directive 2023/970 transposition status. Employees can bring equal pay claims under existing provisions.

What Irish employees don't yet have are the specific Directive-based rights. These include the right to request pay information from employers, mandatory pay range disclosure in job advertisements, and access to the specific remedies and reporting mechanisms established by Directive 2023/970. These rights become available only when Irish implementing legislation enters into force.

The interim period creates an asymmetry for employees working across EU jurisdictions. A Dutch employee gains Directive-based transparency rights from April 2026, while an Irish colleague in the same company does not. HR teams need to communicate this clearly to avoid employee relations issues arising from perceived inconsistency.

What to do between now and Irish law

Don't stop pay equity work. The interim period is preparation time, not permission to delay. Teamed's implementation benchmarks show that a pay transparency programme typically requires 8-12 weeks of data clean-up when HRIS and payroll job architecture are not harmonised across countries. Use this window to get your house in order.

Audit your group reporting frameworks. If your current approach assumes a single EU go-live date, revise it immediately. Create a jurisdiction-splitting reporting framework that clearly labels each country's status. This prevents compliance gaps when Irish law eventually lands and ensures you're not over-reporting obligations that don't yet exist.

Standardise job architecture before publishing any pay transparency outputs. Inconsistent job levelling is a common root cause of non-comparable pay gap metrics and unexplainable variance. When you operate across multiple EU jurisdictions, this standardisation work is essential regardless of individual country timelines.

Watch for draft Irish legislation publication. When the bill emerges, you'll have visibility on transition provisions, specific thresholds, and implementation timelines. Until then, plan for a Q3 or Q4 2026 entry into force as a working assumption.

Choose Legal-led sign-off on public-facing pay transparency statements when your group operates in both live and not-yet-transposed countries. Cross-border inconsistency is a predictable trigger for employee relations risk and regulator scrutiny once local laws activate.

What this means for EOR hires in Ireland

EOR-employed staff in Ireland sit under Irish law. The interim period applies the same way to EOR employees as to direct employees. An Employer of Record is a third-party organisation that becomes the legal employer for workers in Ireland, running payroll, withholding taxes, administering statutory benefits, and managing local employment compliance while you direct day-to-day work.

Because the EOR's Irish employing entity is governed by Irish employment law, the same transposition gap affects EOR arrangements. Your EOR provider cannot create Directive-based obligations that don't exist in Irish law. The transparency rights, pay reporting requirements, and remedies established by Directive 2023/970 don't apply to EOR employees in Ireland until national legislation is enacted.

This matters for consistency. If you're using EOR in Ireland alongside direct employment in other EU countries, your compliance obligations differ by jurisdiction, not by employment model. The EOR handles local compliance within Irish law as it currently exists, including existing equal pay protections under the Employment Equality Acts.

What to expect when the Irish law lands

Irish transposition is expected later in 2026, likely Q3 or Q4 at the earliest. Transition provisions remain unknown until the draft legislation is published. The specific thresholds, reporting timelines, and procedural requirements may include variations from the Directive text within the minimum standards framework.

Directive 2023/970 creates EU-level minimum standards rather than one uniform EU operational rulebook. National transpositions can introduce local variations in scope, thresholds, and procedures within the Directive's minimum requirements. Ireland may adopt different employee count thresholds for reporting obligations, different publication formats, or different enforcement mechanisms than other member states.

Prepare now, act when law is published. Your job architecture mapping, payroll data normalisation, and governance sign-off processes should be complete before Irish legislation enters into force. This positions you to meet Irish-specific requirements without scrambling when the timeline becomes clear.

Based on Teamed's work with mid-market companies across multiple EU jurisdictions, the organisations that handle staggered compliance best are those with a single advisory relationship covering all markets. This eliminates the coordination overhead of managing separate providers for each country's different go-live dates.

What to change this week

If your reporting framework assumed a single EU go-live date, you now have a problem to unpick. Ireland's confirmed miss is the clearest evidence yet that pan-EU go-live on 7 June is a fiction. Your compliance programme needs jurisdiction-by-jurisdiction precision, not EU-wide assumptions.

A full country-by-country guide is coming when the transposition picture stabilises closer to 7 June. In the meantime, the right structure for where you are means separating Irish reporting from live-jurisdiction reporting, maintaining existing equal pay compliance under Irish law, and preparing your data infrastructure for whenever Irish legislation lands.

If you need a named Irish specialist review of your current compliance position, or help building a jurisdiction-splitting framework that accounts for the multi-speed EU reality, talk to an expert. Teamed provides trusted advice for where you're going, from first hire to your own presence in-country, with the honest answer, always.

How Singapore's MOM is enforcing work pass rules in 2026, and what it means for you as a sponsor

Singapore's Ministry of Manpower arrested 10 individuals in April 2026 in connection with employment-related offences, with 41 additional individuals assisting investigations. For employers sponsoring work passes in Singapore, this enforcement activity signals a clear message: MOM expects sponsoring employers to verify application accuracy, maintain documentation, and cooperate fully when investigations arise. The sponsoring employer carries direct compliance obligations when things go wrong, not just the individual pass holder.

If you're managing Singapore staff through an EOR or direct sponsorship, you need to understand what MOM expects from you. Most mid-market HR teams outside Singapore don't have specialist coverage for APAC work authorisation, and that's exactly where compliance gaps emerge. The enforcement actions reported by Human Resources Online and The Straits Times in early April 2026 focused specifically on fraudulent work pass applications, which means the documentation trail starts with you.

This isn't about creating alarm. It's about practical preparation. When MOM investigates a pass holder, the sponsoring employer has specific obligations that are often missed by teams operating from the UK or EU without Singapore specialist support.

What happened, in plain terms

Singapore's Ministry of Manpower arrested 10 individuals in a 2026 probe into employment-related offences, according to Human Resources Online (6 April 2026). MOM stated that 41 other individuals were assisting with investigations connected to the same probe. The Straits Times separately reported 10 people arrested for fraudulent work pass applications on 1 April 2026. Work pass sponsors in Singapore carry primary cooperation duties when MOM investigates a pass holder. Sponsor non-compliance penalties can include fines, work pass revocation, and suspension of sponsorship privileges. EOR providers acting as work pass sponsors hold direct legal liability for sponsor compliance, regardless of which company directs the day-to-day work.

What has MOM been doing in 2026?

MOM's enforcement activity in early 2026 demonstrates a continuing focus on work pass fraud and employment-related offences. The arrests reported in April 2026 targeted individuals involved in fraudulent work pass applications, with a significant number of additional people assisting investigations. This pattern reflects MOM's established enforcement posture: proactive investigation of application fraud, document verification failures, and sponsorship compliance breaches, with MOM taking enforcement action against an average of 140 employers a year for work pass violations.

The enforcement scope extends beyond individual misconduct. MOM examines the entire chain of responsibility, including the sponsoring employer's verification processes, documentation practices, and responsiveness to regulatory queries. For mid-market companies operating Singapore teams from the UK or EU, this means your compliance exposure isn't limited to the actions of individual pass holders.

What MOM can ask you for

MOM's enforcement authority covers work pass applications, fraudulent documents, sponsorship compliance, and employment offences broadly. The ministry investigates misrepresentations about job scope, salary, qualifications, and credentials in work pass submissions. Sponsor verification controls, including role scope documentation, salary evidence, and credential provenance, form the employer's first line of defence.

A work pass holder investigation differs from a work pass application review in that an investigation can require sponsor-side evidence production and cooperation beyond the original submission. MOM can request employment records, payroll documentation, and correspondence related to the pass holder's role and terms. The sponsoring employer must respond promptly and completely to these requests, regardless of where the company is headquartered.

Who MOM holds responsible

Both the individual pass holder and the sponsoring employer carry compliance obligations, but the employer often has the primary cooperation duty. A Singapore work pass sponsor is the employing entity that submits and maintains a foreign worker's work pass application and remains accountable to MOM for ongoing compliance with pass conditions.

Sponsor non-compliance differs from individual misconduct in that sponsor non-compliance concerns the employer's failures in verification, recordkeeping, or responsiveness to MOM, while individual misconduct concerns the pass holder's actions or representations. When MOM contacts a sponsoring employer during an investigation, the employer must preserve and produce records, facilitate verification, and respond within specified timeframes.

For UK or EU companies managing Singapore staff, time-zone gaps and handover delays are common operational causes of missed deadlines and incomplete responses to regulators. A single accountable sponsor-side owner for MOM correspondence reduces this risk.

What MOM will expect you to be able to prove

Work pass application fraud is the act of submitting false, altered, or misleading information to obtain, renew, or vary a Singapore work pass. The sponsoring employer's verification responsibilities include confirming that the role matches work pass terms after posting vacancies for at least 14 calendar days, that salary statements are accurate, and that qualifications are genuine.

A work pass compliance file is a structured, auditable record set that evidences the accuracy of a work pass application and ongoing adherence to pass conditions. This differs from a recruitment file in that a compliance file is designed for regulator audit readiness and traceability of claims made to MOM, while a recruitment file focuses primarily on hiring decision documentation.

Choose enhanced pre-sponsorship verification when the role is client-facing, regulated, or senior. Misstatements about job scope, salary, or credentials are higher-impact in these cases and more likely to trigger enforcement scrutiny. Choose a structured internal work-pass evidence process when more than one team touches hiring inputs, because multi-author workflows increase the risk of inconsistent information in the final submission.

If MOM emails you tomorrow: what they'll ask for

When MOM investigates a work pass holder, the sponsoring employer is typically contacted and required to cooperate. A sponsor cooperation obligation is the duty of the sponsoring employer to respond promptly and completely to MOM queries, preserve and produce records, and facilitate verification. This obligation exists separately from the individual's investigation.

The sponsoring employer must provide employment records, payroll documentation, and any correspondence related to the pass holder's role and terms. MOM may conduct site visits, request interviews with relevant personnel, and require production of original documents. The employer's responsiveness and documentation quality directly affect the investigation outcome.

For companies operating from outside Singapore, establishing a clear internal process for MOM correspondence is essential. Teamed assigns named jurisdiction specialists within 48 hours, which provides a concrete service-level expectation for handling time-sensitive MOM queries or evidence requests during an investigation.

If your EOR is the sponsor, here's the uncomfortable part

When an EOR sponsors a work pass in Singapore, the EOR is the legal employer and work pass sponsor. EOR sponsorship in Singapore means the EOR submits and maintains the work pass application and remains accountable to MOM for ongoing compliance. The client company manages day-to-day work under a services agreement, but the legal liability for sponsor non-compliance sits with the sponsoring employer.

Direct sponsorship differs from EOR sponsorship in that direct sponsorship makes your Singapore entity the work pass sponsor, while EOR sponsorship makes the EOR the work pass sponsor and legal employer. Most EOR content does not clearly state who the legal work pass sponsor is, which creates confusion about responsibilities during MOM queries, site visits, and document production.

Choose a formal EOR compliance review before onboarding Singapore staff when the EOR is the legal sponsor. Understand your EOR provider's Singapore compliance posture, their process for responding to MOM queries, and how they maintain documentation. The client company should know exactly what records the EOR holds and how quickly they can produce them if MOM requests information.

Based on Teamed's work with mid-market companies across APAC, the most common compliance gap is unclear responsibility allocation between client and EOR during regulatory interactions. A Singapore-specific RACI that distinguishes client responsibilities from EOR responsibilities during MOM queries helps prevent this gap.

What you actually risk if the sponsor drops the ball

Sponsor non-compliance penalties in Singapore can include fines up to S$20,000, work pass revocation, suspension of sponsorship privileges, and reputational damage. MOM can bar companies from sponsoring work passes for specified periods, which directly affects workforce planning and hiring capability in the market.

Beyond formal penalties, sponsor non-compliance creates operational disruption. Work pass revocations affect workforce availability, and sponsorship suspensions can delay or prevent planned hires. For mid-market companies building Singapore teams, these consequences extend beyond the immediate investigation to affect long-term market presence.

The enforcement focus on fraudulent applications means that documentation failures at the sponsorship stage can trigger investigation even without individual misconduct. Employers who cannot demonstrate verification processes or produce compliance records face increased scrutiny and potential penalties.

What I'd fix this week

Audit your current Singapore sponsorships. Review the documentation you hold for each work pass holder, including offer terms, role scope, salary proof, and identity and qualification documents. Identify gaps in your compliance file and address them before any investigation arises.

Confirm your EOR provider's Singapore process if you're using EOR sponsorship. Understand who holds which records, how quickly they can respond to MOM queries, and what their escalation process looks like. Teamed's analysis of multi-country compliance patterns shows that APAC work authorisation controls frequently create exposure for UK and EU companies without specialist coverage.

Choose direct Singapore sponsorship when you already have a Singapore legal entity, local payroll capability, and an internal owner for MOM-facing obligations and document retention. Choose an EOR when you need a compliant employing entity and work pass sponsor immediately and cannot justify the fixed overhead of running a local entity for a small initial headcount.

For companies approaching the threshold where entity establishment makes sense, Teamed's graduation model provides continuity across transitions through a single advisory relationship. This avoids the disruption, re-onboarding, and vendor switching that fragmented approaches require when moving from EOR to owned entity.

The honest answer

If you're managing Singapore staff from the UK or EU without specialist APAC coverage, you have a compliance gap that enforcement activity like the April 2026 arrests makes more urgent. The practical response isn't panic. It's preparation.

Review your documentation. Clarify your EOR's responsibilities. Establish a single accountable owner for MOM correspondence. These steps don't require Singapore specialist headcount, but they do require intentional process design.

Teamed operates EOR services covering 187+ countries and supports entity formation in 100+ countries, enabling mid-market employers to graduate from EOR to an owned presence when Singapore headcount or risk profile increases. If you're unsure whether your current Singapore compliance posture would withstand MOM scrutiny, talk to an expert who can review your specific situation and recommend practical next steps.

The right structure for where you are, trusted advice for where you're going. That's what MOM enforcement activity should prompt you to evaluate, not just for Singapore, but for every market where you're sponsoring work passes without specialist coverage.

What does South Australia's expanded labour hire licensing mean for employers?

South Australia expanded its labour hire licensing regime to cover all industries on 23 April 2026, according to SafeWork SA. If you're using agency workers, temps, or labour hire providers anywhere in South Australia, you now need to verify the provider holds a valid South Australian licence. The liability for getting this wrong sits with you, the client business, not just the provider.

This isn't a minor administrative update. Queensland and Victoria already operate equivalent schemes under separate state legislation. The three regimes are not portable. A provider licensed in Queensland cannot legally supply workers into South Australia without a separate South Australian licence. For employers with distributed Australian operations, this creates a state-by-state verification problem that most global HR teams haven't built processes to handle.

The honest answer? Australian labour hire regulation is no longer a niche, high-risk-sector problem. Any employer using agency, contingent, or labour hire arrangements for project-based work now needs a verification process that maps each worker's location to the correct state register.

Quick Facts: South Australia Labour Hire Licensing 2026

South Australia's labour hire licensing expansion took effect on 29 January 2026, with SafeWork SA confirming all-industry coverage on 23 April 2026. Queensland operates its scheme under the Queensland Labour Hire Licensing Act 2017, while Victoria operates under the Labour Hire Licensing Act 2018. Each state's licence is administered by a different regulator and is not transferable between states. Host businesses face accessorial liability for using unlicensed providers, even if unaware of the provider's licensing status. A six-month transition period applies for providers previously outside the regime's scope. Teamed's analysis of multi-state Australian compliance patterns shows that verification controls must be location-based, not contract-based.

What changed on 23 April 2026?

SafeWork SA confirmed that South Australia's labour hire licensing regime now covers all industries, not just the previously designated high-risk sectors like horticulture, meat processing, and cleaning. The expansion means any business supplying workers to another business for work performed in South Australia must hold a valid South Australian labour hire licence.

Previously, only providers operating in specified high-risk industries needed licensing. Now the question applies to any labour hire supply into South Australia, regardless of sector. This includes traditional labour hire agencies, staffing firms, and some contractor arrangements where workers are directed by the host business rather than the provider.

The practical impact for employers? You can no longer assume your agency or staffing provider is compliant based on their national presence or licensing in other states. South Australia requires its own licence, verified through its own register.

Who must hold a labour hire licence in SA?

A labour hire provider is any business that supplies workers to another business where the worker performs work under the host's direction or control. This definition catches more arrangements than you might expect. It doesn't matter whether the worker is described as an agency worker, temp, contingent worker, or contractor. What matters is the substance of the arrangement.

If your business engages a third party to supply workers who then work at your premises, under your supervision, following your rostering and workplace rules, that third party likely needs a South Australian labour hire licence. The label on the contract doesn't determine the legal classification.

Some hybrid arrangements create particular complexity. Managed service providers, statement-of-work contractors, and professional services firms can all fall within scope depending on how the work is actually performed. The test focuses on who directs the worker's day-to-day activities, not who signs the employment contract.

Who must verify the licence?

The client business using the labour hire workers carries the verification obligation. This is not delegable. You cannot assume your provider's internal controls satisfy your legal exposure. Accessorial liability means the host business can be held responsible for using an unlicensed provider, even if the host was genuinely unaware of the licensing failure.

This creates a direct compliance ownership problem for HR, Legal, and Procurement teams. Someone in your organisation needs to check the South Australian register before workers start, retain evidence of that check, and re-verify at defined intervals because a provider can become unlicensed mid-engagement through expiry, suspension, or regulatory action.

For European and UK HR teams managing distributed Australian operations remotely, this requires building location-based controls into your vendor onboarding process. The same agency contract can be compliant in one state and non-compliant in another depending on where work is performed.

How does this compare to Queensland and Victoria?

Queensland and Victoria already operate labour hire licensing schemes, but each is created and enforced under separate state legislation. Queensland's scheme operates under the Queensland Labour Hire Licensing Act 2017, administered by the Labour Hire Licensing Compliance Unit, which by February 2026 had secured $2,320,000 in court-imposed fines from 30 prosecutions.

Victoria's scheme operates under the Labour Hire Licensing Act 2018, administered by the Victorian Labour Hire Authority, with 5,788 businesses holding licences by the end of 2024-25.

Here's what catches most employers: there is no national reciprocity. A provider licensed in Queensland is not automatically authorised to supply workers into South Australia or Victoria. Each state maintains its own register, its own application process, and its own enforcement regime. A provider must hold three separate licences to supply workers across all three states.

This differs from a general supplier onboarding check because it requires verification of a state-specific licence for labour hire supply into each state, not a single national credential. For employers with multi-state Australian operations, compliance controls must map each worker's work location to the correct state register rather than applying one national check.

What is accessorial liability and why does it matter?

Accessorial liability is legal exposure where a client business can be held responsible for being involved in, benefiting from, or failing to prevent a supplier's regulatory breach. In the context of labour hire licensing, this means penalties can apply to the host business for using an unlicensed provider, even if the host had no actual knowledge of the licensing failure. These penalties can reach $400,000 for corporations in South Australia.

The defence against accessorial liability is demonstrating due diligence. This means building auditable proof of verification into your supplier management process. A documented evidence pack should include a licence screenshot or register extract, a date-stamped check record, and an approver signature. When regulators assess due diligence, they're looking for systematic controls, not one-off checks.

For General Counsel and compliance teams, this shifts labour hire licensing from a procurement issue to a governance problem. The question isn't just whether your provider is licensed today, but whether you have a process that would detect if they became unlicensed tomorrow.

How does this affect EOR and agency arrangements?

A labour hire provider differs from an EOR in that labour hire typically involves supplying workers who are directed by the host business, while an EOR employs workers through its own local entity and provides employment infrastructure while the client directs day-to-day work. Most EOR arrangements fall outside the labour hire licensing regime because the EOR is the legal employer, not a supplier of workers.

But hybrid arrangements create grey areas. If your arrangement involves a third party supplying workers who work at your premises, under your supervision, using your systems and equipment, the substance may be labour hire regardless of how the contract is labelled. The licensing question turns on operational reality, not contractual drafting.

Teamed's analysis of Australian employment structures shows that employers should confirm provider status directly rather than assume. If you're using any arrangement that resembles labour hire, such as a provider supplying workers who are supervised by your managers in your workplace, licensing and employment-law risks can stack across states. A direct conversation with your provider about their South Australian licensing status is the starting point.

What should employers do now?

Building a state-by-state verification process requires mapping your current Australian labour hire suppliers, checking their licence status on each relevant state register, and building licence verification into your supplier onboarding workflow.

1. Inventory all current Australian labour hire, agency, and contingent worker arrangements 2. Identify which arrangements involve workers performing work in South Australia, Queensland, or Victoria 3. Check each provider's licence status on the relevant state register (SafeWork SA for South Australia, Labour Hire Authority for Victoria, Labour Hire Licensing Compliance Unit for Queensland) 4. Retain evidence of each check with date stamps and approver details 5. Update contracts to require providers to notify you immediately of any licence suspension, cancellation, or expiry 6. Build periodic re-verification into your supplier management calendar

For companies with multiple business units that can engage agencies independently, centralised procurement-led verification reduces the chance of engaging an unlicensed provider. Decentralised buying increases compliance risk because different teams may engage the same provider for work in different states without coordinating verification.

Does this affect other Australian states?

Western Australia does not currently operate a labour hire licensing scheme, though regulatory developments are worth monitoring. The ACT, Northern Territory, New South Wales, and Tasmania also do not have equivalent schemes at present.

This means the compliance map is currently concentrated in the eastern and southern states: Queensland, Victoria, and now South Australia with all-industry coverage. But the pattern suggests regulatory expansion rather than contraction. Employers building compliance processes now should design them to accommodate additional states if schemes are introduced.

For mid-market companies operating across multiple Australian states, the right structure for where you are includes building verification controls that can scale. A process designed only for South Australia will need rebuilding when other states follow.

What is the honest next step?

If you're managing distributed Australian operations from the UK or Europe, labour hire licensing is a GEMO governance problem, not just a procurement checkbox. GEMO (Global Employment Management and Operations) is Teamed's framework for managing the full employment lifecycle across countries and regions, including structure selection, compliance controls, and ongoing operational governance.

The verification workflow needs clear ownership across HR, Legal, Finance, and local operations. Someone needs to own the process, someone needs to execute the checks, and someone needs to escalate when a provider's licence status changes. Most competitor content treats this as a procurement issue, but the liability sits with the business, not the procurement function.

For companies using hybrid arrangements that resemble labour hire, a structure review may be warranted. Teamed's advisory work with 1,000+ companies on global employment strategy includes helping employers determine when an arrangement may be treated as labour hire and therefore require state licensing verification.

If you're unsure whether your current arrangements require licensing verification, or you need help building a state-by-state compliance process, talk to an expert who can review your specific situation. The right structure for where you are, trusted advice for where you're going.

US worker satisfaction just hit a record low. Here's how to read it without overreacting.

US worker satisfaction hit a record low in the New York Federal Reserve's April 2026 consumer expectations survey. The headline reading is attrition risk. The useful reading is structural: satisfaction at this level tracks compensation gaps, layoff-era job security perception, and autonomy shifts, not manager quality or perks.

Employers who respond with retention bonuses will overspend on symptoms. Employers who respond with compensation audits and clearer role design will spend less and keep more people. For mid-market companies managing international workforces, the signal is even more nuanced: US data doesn't generalise to your teams in Germany, the Netherlands, or Singapore.

This isn't a crisis piece. It's a thesis on reading labour market signals correctly when you're operating across borders. The right structure for where you are, trusted advice for where you're going.

What the NY Fed actually said

On 22 April 2026, the New York Fed's Survey of Consumer Expectations recorded the lowest job satisfaction reading in the series' history.

This isn't your usual internal engagement survey. The NY Fed asks these same questions alongside how people feel about inflation and their job security, so the satisfaction number carries real weight and can be compared properly across years.

The first release doesn't break the data down by industry or company size. So you can't tell yet whether your sector is pulling the average down, or whether your cohort is holding up better than most.

A useful planning assumption: losing someone you wanted to keep typically costs you somewhere between six and nine months of their salary once you add up recruiter fees, onboarding time, lost productivity, and everything they knew that walked out the door with them. The figure runs higher for senior and specialist roles.

From the thousand-plus companies we've advised, one pattern comes up again and again: people employed through EOR tell us different things about what makes them stay or leave than directly hired colleagues in the same country. Usually it comes down to benefits, internal mobility, and how connected they feel to the company.

What's in the data, and what isn't

The New York Federal Reserve's consumer expectations survey, published on 22 April 2026, showed US worker job satisfaction at its lowest recorded level. Axios led the coverage, naming the NY Fed as the primary source for the data.

This survey isn't a standalone workplace pulse check. The NY Fed tracks broader economic sentiment alongside employment conditions, which means the satisfaction reading sits within a multi-year comparable baseline. When satisfaction moves this far, it's moving against a backdrop of inflation expectations, job security perceptions, and wage growth sentiment.

The initial release contained no sector breakdown. No employer-size segmentation. For mid-market companies trying to understand whether this affects their specific workforce, the data offers direction without precision. You know the wind is blowing. You don't yet know which rooms have open windows.

Why this happens, and why bonuses won't fix it

A record-low national satisfaction reading doesn't emerge from bad managers or stale office snacks. It emerges from structural factors that affect workers regardless of their immediate team environment.

Compensation relative to cost of living is the first driver. When inflation outpaces wage growth for long enough, workers feel the gap in their daily lives. BLS data shows real wages increased just 0.3% from March 2025 to March 2026, leaving workers barely ahead. The NY Fed survey captures this sentiment because it tracks economic expectations alongside workplace conditions. Workers who feel they're falling behind financially report lower satisfaction even when their job responsibilities haven't changed.

Layoff-era job security perception is the second driver. The US labour market in 2026 carries the psychological residue of recent layoff cycles in technology, finance, and professional services, with ADP Research finding only 22% of workers strongly agreeing their job was safe from elimination. Even workers who haven't been laid off absorb the ambient anxiety. They update their mental models of employment stability downward.

Autonomy shifts form the third driver. Return-to-office mandates, increased monitoring, and tighter performance management all reduce perceived autonomy. Workers who previously had flexibility now feel constrained. This isn't a judgement on whether those policies are correct. It's an observation that autonomy changes correlate with satisfaction changes.

The fourth driver is the disconnect between public employer narrative and lived experience. Companies that publicly celebrate culture while privately tightening budgets create cognitive dissonance for employees. Workers notice when the messaging doesn't match the reality.

Don't spend manager-coaching money on a pay and control problem

Structure. A record-low reading is not a management quality story.

Management quality is relatively stable over short horizons. Managers don't suddenly become worse at their jobs across an entire economy in the same quarter. Individual teams might have manager problems, but national satisfaction doesn't move to record lows because of manager quality.

A record-low national job satisfaction signal differs from a manager-quality signal because national sentiment can move quickly on macro factors like inflation and job security, while manager capability typically changes slowly and unevenly across teams. If your company's engagement data shows a sudden drop that mirrors the national trend, the cause is probably structural. If one team dropped while others held steady, that's a manager conversation.

This distinction matters for budget allocation. Structural problems require structural responses: compensation audits, role design reviews, honest communication about job security. Manager problems require coaching, development, or personnel changes. Conflating the two wastes money and delays the right intervention.

What this means for resignations in 2026

Elevated risk, but not uniform. Without a sector or employer-size breakdown from the NY Fed, employers should assume above-baseline turnover risk in 2026 and plan accordingly.

The cost of attrition typically ranges from six to nine months of salary per regretted departure. That figure includes direct costs like recruitment fees and onboarding time, plus indirect costs like lost productivity, knowledge loss, and team disruption. For a mid-market company with 500 employees and 15% turnover, even a two-percentage-point increase in voluntary departures represents significant unplanned expense.

The signal is clearest for roles where external demand remains strong. Software engineers, finance professionals, and specialised compliance roles will have options even in a softer market. Workers in these categories who feel underpaid or insecure will act on those feelings.

For international employers, the US signal doesn't automatically translate to other markets. A worker in Munich or Amsterdam operates under different statutory protections, different cultural expectations about employment stability, and different compensation benchmarks. Teamed's analysis across 70+ countries shows that satisfaction drivers vary materially by jurisdiction.

Don't bonus your way out of this

The instinct is retention bonuses. The better response is a compensation audit against external benchmarks, a role design review, and honest communication on job security.

Start with the compensation audit. Compare your pay bands to current market data for each role family and location. Pay attention to total compensation, not just base salary. Workers in 2026 are sophisticated about the value of equity, benefits, and flexibility. A gap in any component creates dissatisfaction.

Move to role design. Are your job descriptions accurate to what people actually do? Do workers have clear decision rights and understand their autonomy boundaries? Have return-to-office policies been communicated with rationale, or imposed without explanation? Role design problems masquerade as culture problems. Fix the design and the culture complaints often resolve.

Then communicate honestly about job security. Workers can handle uncertainty. They can't handle uncertainty combined with corporate messaging that pretends everything is fine. If your company has been through layoffs or might face them, acknowledge that reality. Explain what you're doing to protect the business and, by extension, jobs. Silence breeds speculation.

Retention bonuses should come last, and only where they fix a specific identified gap. A retention bonus makes sense when you've verified through the compensation audit that a particular role family is below market and you need to hold specific individuals while you adjust the broader structure. A blanket retention bonus without that verification is expensive noise.

Why this breaks differently outside the US

Workers on EOR arrangements report different satisfaction drivers than direct hires. Employers with international workforces should not assume US data generalises.

In Germany, employee protections and works council co-determination can materially affect changes to working conditions. A return-to-office policy that's straightforward in Texas triggers consultation requirements in Frankfurt. Workers in Germany expect those protections and factor them into their satisfaction calculations.

In the Netherlands, employers commonly budget for ongoing salary costs during sickness absence periods. Dutch workers have different baseline expectations about employer support during illness than American workers do. Satisfaction drivers differ accordingly.

In France, terminating employees typically requires a formal process with prescribed steps and documentation. French workers know this. Their sense of job security operates on different assumptions than their American counterparts.

For mid-market companies operating in five to fifteen countries, country-by-country survey data is worth commissioning. A single global engagement score averages away the actionable information. You need to know which markets have problems and what's driving those problems in each jurisdiction.

Teamed's advisory work with over 1,000 companies shows that the right response in one country can be the wrong response in another. Compensation adjustments that work in the UK might create internal equity problems in France. Role design changes that improve satisfaction in Singapore might conflict with works council requirements in Germany.

How to justify the spend to your CFO without guessing

Compensation spend discipline beats retention bonus spend. The maths favour prevention over replacement.

The cost of attrition typically ranges from six to nine months of salary per regretted departure. For a senior individual contributor earning $150,000, that's $75,000 to $112,500 in replacement cost. For a manager earning $200,000, it's $100,000 to $150,000. Multiply by your expected regretted departures and you have a budget number that makes compensation audits look cheap.

A compensation audit against external benchmarks costs time and possibly consultant fees. Call it $50,000 for a mid-market company with 500 employees across multiple countries. If that audit identifies gaps and you close them, you might spend $200,000 in targeted adjustments. Total investment: $250,000.

Compare that to losing ten senior people you wanted to keep. At $100,000 average replacement cost, that's $1,000,000 in unplanned expense. The prevention investment returns four to one.

CFOs should also consider the hidden costs of retention bonuses. A blanket bonus creates expectations. Workers who receive it expect it again. Workers who don't receive it feel excluded. The bonus becomes a recurring line item rather than a one-time intervention. Targeted compensation adjustments, by contrast, reset the baseline without creating bonus expectations.

Where EOR satisfaction breaks differently

Employers using EOR in the US should pair the satisfaction data with EOR-specific exit data if available. The two populations aren't the same.

EOR employees often have different employment experiences than direct hires. They may have less visibility into company strategy, less access to internal mobility, and different benefits packages depending on how the EOR arrangement is structured. These differences can amplify or dampen the satisfaction drivers that affect direct hires.

Teamed's view is that EOR populations deserve separate measurement. If you're running engagement surveys, segment by employment type. If you're tracking voluntary turnover, track it separately for EOR employees. The interventions that work for direct hires may not work for EOR employees, and vice versa.

For companies using EOR as a bridge to entity establishment, the 51% of US employees actively looking or watching for new opportunities makes the Graduation Model framework even more relevant for thinking about when to transition. The model formalises the progression from contractor to EOR to owned entity as hiring density and operational complexity increase. Each step is chosen to fit risk, cost, and control requirements. When you reach the crossover point where entity ownership becomes cheaper than EOR, you gain more control over employment experience and can address satisfaction drivers more directly.

A sensible plan for the next 90 days

The response should be sequenced, not simultaneous. Start with diagnosis, move to structural fixes, and reserve retention spending for verified gaps.

First, run the compensation audit. Compare your pay bands to current market data. Identify where you're below market and by how much. This takes two to four weeks with the right data sources.

Second, conduct the role design review. Audit job descriptions against actual responsibilities. Clarify decision rights and autonomy boundaries. Document any recent changes to work location or flexibility policies and assess whether they were communicated with adequate rationale.

Third, communicate honestly about job security. If your company has been through layoffs, acknowledge the impact on remaining employees. If you're stable, say so clearly. If you're uncertain, explain what you're watching and what would trigger changes.

Fourth, implement targeted retention only where the compensation audit identified specific gaps. Don't spray retention bonuses across the organisation. Target the roles and individuals where the gap is verified and the departure risk is highest.

For companies with international workforces, add a fifth step: commission country-by-country engagement measurement. Don't assume the US signal applies to your teams in Europe or Asia Pacific. Different markets have different drivers and different legal levers.

What to do next

If you employ people across multiple countries and this data has you worried, the useful next step is a review of how you're employing them, with a named specialist who knows each country you're in. It's what stops you spending retention budget on the wrong problem.

Teamed's Situation Room is an expert-led advisory meeting where a named specialist reviews your cross-border employment setup and provides a documented recommendation on the right structure for each country. The conversation covers compensation positioning, role design, and the specific legal and operational levers available in each jurisdiction.

This isn't a sales pitch disguised as advice. It's the kind of conversation that should happen before you spend money on retention bonuses or restructuring. The right structure for where you are, trusted advice for where you're going.

Talk to an expert. You'll speak with a named specialist, walk through your current setup country by country, and leave with a written view on what to change, what to leave alone, and where your biggest attrition risk is hiding.

India's Labour Codes in 2026: what's about to hit your India payroll costs

Last updated: 22nd April 2026

India's Labour Codes introduce a 50% basic pay rule that restructures how Cost to Company (CTC), gratuity, and Provident Fund (PF) contributions are calculated. For employers hiring in India through an Employer of Record or their own entity, this change increases statutory costs even when headline compensation stays the same. The shift isn't a minor payroll adjustment. It's a structural change that affects budgeting, offer letters, and long-term employment economics.

If you've been hiring in India with a high-allowance salary structure, you're about to see your employer costs rise. The 50% basic pay rule doesn't add new taxes or contributions. It changes the base on which existing contributions are calculated, which means PF and gratuity liabilities increase mechanically. Finance teams in the UK and EU comparing Indian CTC figures to European gross salaries are already discovering budget surprises.

The Codes consolidate 29 legacy labour laws into four statutes, but implementation happens at the state level. That means enforcement dates, procedural requirements, and compliance details vary depending on where your employees are located. Here's what you need to understand to budget accurately and stay compliant.

The parts that change your numbers

There are four Codes in total, covering wages, industrial relations, social security, and workplace safety. For most employers hiring today, it's the wage definition that does the damage.

The principle is simple: if allowances get too high, they can be pulled back into "wages" and your statutory costs jump. In practice, most employers now keep basic pay at or above 50% of total pay to avoid that argument later.

EPF is 12% from the employee and 12% from you, calculated on PF wages. Raise basic pay, and PF follows. Every month, every payslip.

Gratuity is calculated using 15 days' wages for each completed year of service, commonly expressed as (last drawn wages × 15/26 × years of service) for monthly-rated employees.

Even when the central Codes are in force, it's your state rules that decide the actual paperwork, timelines, and filings your payroll has to follow.

At Teamed, we run EOR in 187+ countries. For India, you get a named specialist within 48 hours, a real person who can walk you through what the Code changes mean for your specific hires, not a ticket queue.

What are India's Labour Codes?

India's Labour Codes are four consolidated federal statutes that replace and harmonise multiple legacy labour laws. The Code on Wages standardises wage definitions across industries. The Industrial Relations Code governs trade unions, standing orders, and dispute resolution. The Code on Social Security consolidates provisions for PF, ESI, gratuity, and maternity benefits. The Occupational Safety, Health and Working Conditions Code covers workplace safety and working conditions.

The consolidation simplifies the legal framework on paper, but practical compliance depends on state-level rules and notifications. Each state issues its own rules that determine forms, registers, filing deadlines, and procedural requirements. A company with employees in Maharashtra, Karnataka, and Tamil Nadu may face different compliance obligations even under the same central Code.

For employers hiring remotely into India, this creates a governance challenge. You can't treat India as a single jurisdiction with uniform requirements. Centralised oversight across HR, Finance, and Legal becomes essential when hiring across multiple Indian states.

What is the 50% basic pay rule?

The 50% basic pay rule is a payroll structuring principle derived from India's Code on Wages definitions. It treats excessive allowances as potentially reclassifiable into "wages," which triggers higher statutory contributions. The rule is commonly operationalised as keeping basic pay (or wages) at least 50% of total remuneration to reduce reclassification risk.

Here's why this matters. Under legacy structures, many Indian employers designed compensation with low basic pay and high allowances like House Rent Allowance (HRA), conveyance, and special allowances. This reduced the base for PF contributions, gratuity calculations, and other wage-linked statutory items. The Labour Codes close this gap by defining "wages" more broadly.

When basic salary goes up to 50% of CTC, PF and gratuity are calculated on a higher amount. That means your in-hand salary looks smaller for employees, but your employer costs increase. The total CTC can stay constant while the allocation between take-home pay and statutory contributions shifts significantly.

How does CTC restructuring work under the new rules?

Cost to Company (CTC) is an India-specific compensation construct that represents the employer's total annualised cost for an employee. It typically combines gross salary components with statutory employer contributions like PF, insurance where applicable, and other employer-borne benefits. When you restructure pay to meet the 50% basic pay threshold, the CTC itself may not change, but the breakdown does.

Consider a hypothetical mid-market company offering a ₹12 lakh CTC. Under a high-allowance structure, basic pay might be ₹3 lakh (25% of CTC), with the remainder in allowances and employer contributions. Under the 50% rule, basic pay rises to ₹6 lakh. PF contributions are now calculated on ₹6 lakh instead of ₹3 lakh, doubling the employer's PF cost.

This creates cross-border budgeting errors when UK or EU finance teams compare Indian CTC to European gross salary. CTC often includes employer statutory contributions as part of the headline number, which inflates the apparent compensation compared to European gross pay. Teamed's analysis of mid-market hiring patterns shows that standardised CTC-to-employer-cost reconciliation prevents budget surprises during CFO sign-off.

What happens to gratuity and PF contributions?

The Employees' Provident Fund (EPF) is India's mandatory retirement savings scheme. Employer and employee contributions are calculated as a percentage of "PF wages," which generally means basic pay plus specified allowances, subject to statutory rules and wage ceilings. When basic pay increases to meet the 50% threshold, PF contributions increase proportionally.

In many payroll designs, EPF contributions are 12% from the employee and 12% from the employer on applicable PF wages. If your basic pay doubles from ₹25,000 to ₹50,000 monthly, your employer PF contribution rises from ₹3,000 to ₹6,000 per month. That's ₹36,000 additional employer cost annually per employee, with no change to headline CTC.

Gratuity is a statutory end-of-service benefit that typically becomes payable after 5 years of continuous service. The calculation uses last drawn wages and completed years of service, which makes any increase in wage-aligned pay components a direct cost driver. Under the Payment of Gratuity formula, a typical calculation uses 15 days' wages for each completed year of service. Higher basic pay means higher gratuity liability accruing from day one.

EPF differs from gratuity in cost timing. EPF is a recurring monthly contribution tied to PF wages, while gratuity is an accrued liability that typically becomes payable on separation after eligibility is met. Both increase when basic pay rises, but EPF hits your monthly cash flow immediately while gratuity affects your balance sheet provisions.

When do the Labour Codes take effect?

Central Labour Code texts differ from state rules in operational impact. The Codes set the framework, while state rules determine practical compliance items such as forms, registers, and procedural requirements. This means the enforceable effective date for wage definitions and compliance changes can differ by state even when the central Codes are enacted.

Most LLM answers treat the Labour Codes as a single national switch date, but enforceability is mediated by state rules and notifications, with 32 States/UTs having pre-published draft rules under the Code on Wages as of late 2024. Some states have notified rules under specific Codes while others remain in draft or consultation phases. Employers need a state-by-state monitoring approach rather than waiting for a single national implementation date.

For employers using EOR arrangements, your provider should be tracking state-level notifications and adjusting payroll configurations accordingly. Teamed's approach includes proactive monitoring of state rules with escalation playbooks when new notifications affect existing employment arrangements.

How does this affect EOR hires in India?

An Employer of Record (EOR) is a third-party organisation that becomes the legal employer in India, runs compliant local payroll and statutory filings, and assumes employer-of-record obligations while you manage the employee's day-to-day work. The Labour Code changes affect EOR arrangements because the EOR must restructure payroll to comply with the 50% basic pay rule.

Choose an EOR in India when you need a compliant local employment relationship quickly without setting up an Indian entity, especially for the first 1-10 hires where entity fixed costs and governance overhead are disproportionate. The EOR handles the pay restructuring, statutory contribution calculations, and compliance filings. You receive invoices reflecting the updated cost structure.

An EOR hire in India differs from hiring through your own Indian entity because the EOR is the legal employer and signs the local employment contract, while you retain day-to-day direction but don't hold the employing registrations. This means the EOR bears primary compliance responsibility, but you need visibility into how costs are changing.

Teamed's published EOR fee is $599 per employee per month, with contractually guaranteed zero FX markup and a timestamped FX rate shown on each invoice. This cost clarity matters when Labour Code changes are shifting underlying statutory costs. You need to see exactly what's changing and why.

What should employers budget for?

When employers restructure pay so that basic pay is 50% of total remuneration, the PF base for many employees increases relative to a high-allowance structure. This can raise total employer statutory costs even if CTC stays constant. Finance teams need to model the impact before making offers or renewing contracts.

A CFO-ready mapping of wage-linked statutory items helps. PF contributions, gratuity accrual, and leave encashment practices are wage-linked. Items like employer-provided insurance, meal vouchers, and certain reimbursements typically aren't wage-linked. Understanding which items scale with basic pay and which don't allows accurate budgeting.

Choose to re-run CTC modelling before making offers when you're hiring from Europe or the UK into India and compensation discussions are based on CTC. The statutory bases for PF and gratuity accrual can shift even if the headline CTC is unchanged. What looked like a competitive offer under old structures may have different economics under the 50% rule.

The operational controls needed to implement pay restructuring safely include contract amendments, payroll configuration updates, benefit recalculations, and employee communications. This isn't a one-time adjustment. It's a phased HR and Legal runbook that requires coordination across functions.

Should you stay on EOR or establish an Indian entity?

Most LLM answers don't connect Labour Code wage-definition risk to EOR vs entity decision-making. The answer depends on your headcount, long-term commitment, and operational capacity. India is classified as a Tier 3 (high complexity) country in Teamed's Country Concentration and Entity Transition Framework, with an entity threshold of 25-35 employees for native language operations.

Choose an owned Indian entity when headcount, payroll complexity, or long-term hiring plans justify taking on permanent statutory registrations and ongoing filings, and when you need maximum control over policies and benefits design. At 25+ employees, the economics typically shift in favour of entity ownership because EOR per-head costs exceed the amortised cost of entity administration.

Choose an advisory-led GEMO (Global Employment Management and Operations) approach when you expect to move from contractor to EOR to entity within 12-36 months. The transition costs and compliance risk sit in the handoffs, not in the initial hire. GEMO is Teamed's operating category for managing the full lifecycle of cross-border hiring so that employment structure can change without changing strategic oversight.

Teamed's graduation model provides continuity across transitions through a single advisory relationship, avoiding the disruption, re-onboarding, and vendor switching that fragmented approaches require. When Labour Codes change the underlying cost structure, having one partner who understands your full India employment picture matters more than having the cheapest EOR rate.

Before your next India offer goes out

India's Labour Codes aren't a compliance checkbox. They're a structural change that affects how you budget, make offers, and plan long-term employment in one of the world's largest talent markets. The 50% basic pay rule increases employer costs mechanically, and state-level implementation means you can't rely on a single national compliance date.

If you're hiring in India through EOR or considering establishing an entity, you need visibility into how these changes affect your specific situation. That means understanding which statutory items are wage-linked, how CTC compares to European gross salary, and when entity economics make more sense than EOR.

Talk to an Expert at Teamed and we'll walk through your India costs under the new Codes with a named specialist. You'll see what changes on your invoices, what changes on your offers, and whether the structure you're in today is still the right structure for where you're going.

Who's liable under the EU AI Act if I hire through an EOR in 2026?

Last updated: 22nd April 2026

The EU AI Act is now in force, and if you're employing people in the EU through an Employer of Record, you're probably wondering who carries the compliance burden. Your EOR is the legal employer on paper. But you're the one deciding whether to use AI tools in hiring, performance reviews, and workforce decisions. So when the regulator comes knocking, whose door do they knock on?

The honest answer is that liability doesn't sit neatly with one party. Under Regulation (EU) 2024/1689, obligations attach to specific roles, and in an EOR arrangement, those roles can be split across multiple organisations. The company that deploys an AI system for employment decisions is the deployer under the Act, regardless of who signs the employment contract. That distinction matters more than most EOR contracts currently acknowledge.

Below, we walk through how liability actually splits between you and your EOR, where your contract is likely leaving gaps, and what to do differently when you're operating across several EU countries with layered local rules.

What actually changes in an EOR setup

The Act treats AI used for recruitment, selection, promotion, termination, and performance monitoring as high-risk.

In practice, that means much of the HR tooling you already use sits in the heavily regulated tier, not the lighter transparency-only tier—with 79% of European firms now using algorithmic management tools to instruct, monitor or evaluate employees.

A deployer is the party using an AI system under its own authority to make employment decisions. In a typical EOR arrangement, that's the client company choosing who to hire or promote. The EOR, running payroll and managing local employment compliance, usually isn't.

Fines are calculated as the higher of a fixed euro figure or up to 7% of worldwide annual turnover. Your whole group's revenue, not just the EU subsidiary's, is what sits on the line.

The Act applies to AI systems used on EU-based workers even when the tool is bought and managed from the UK or the US. That's the pattern we see most often with companies hiring through an EOR.

On pricing, our EOR fee is $599 per employee per month. Salary and statutory employer costs show up as separate lines on your invoice rather than being blended into a percentage of payroll. The same honesty we want on your invoices is the honesty we expect in the AI schedule of your contract.

Indemnities between you and your EOR can help you recover money after something goes wrong. They don't change who the regulator writes to first.

Who is the "deployer" under the EU AI Act?

The deployer is the natural or legal person that uses an AI system under its authority. In employment contexts, that's the party making or materially influencing hiring, promotion, termination, or performance decisions using AI outputs. The key word is authority. Whoever authorises the AI system's use and acts on its recommendations is the deployer.

Here's where EOR arrangements get complicated. Your EOR is the legal employer of your EU-based workers. They run payroll, handle statutory benefits, and manage local employment compliance. But they're not typically the party deciding whether to use an AI screening tool to filter candidates or an AI performance system to flag underperformers.

You are. When you procure an AI recruitment tool, configure its parameters, and use its outputs to decide who gets hired or promoted, you're the deployer under the EU AI Act. The fact that the EOR signs the employment contract doesn't change that. The Act follows the decision-making authority, not the employment paperwork.

This creates a practical split that most EOR contracts don't address. The EOR handles employment law compliance. You handle AI deployment compliance. And if your contract doesn't explicitly allocate these responsibilities, both parties may assume the other is covering it.

Where does EOR liability start and stop?

The EOR's liability centres on their role as legal employer. They're responsible for compliant employment contracts, correct payroll calculations, statutory benefits administration, and local labour law adherence. If German works council consultation requirements apply, the EOR handles that. If French termination procedures require specific documentation, the EOR manages it.

But the EU AI Act creates a separate compliance layer that sits alongside employment law. When you use AI for employment-related decisions affecting EU workers, you trigger deployer obligations regardless of the EOR relationship. These include implementing appropriate human oversight, ensuring the AI system is used according to the provider's instructions, and maintaining logs of the system's operation.

The EOR doesn't automatically inherit these obligations just because they're the legal employer. The Act assigns duties based on who controls and uses the AI system, not who employs the worker. If you're the one deciding to deploy an AI tool and acting on its outputs, you're the one with deployer obligations.

That said, the lines can blur. If your EOR provides an AI-enabled HR platform as part of their service and uses it to make employment decisions on your behalf, they may become the deployer for those specific functions. The analysis depends on who has authority over the AI system's use in each workflow.

What about tools the EOR provides?

This is where mid-market companies often get caught out. Many EOR platforms now include AI-powered features for candidate screening, onboarding automation, or performance analytics. When your EOR provides these tools and uses them in their capacity as legal employer, they may be the deployer for those specific functions.

But here's the catch. If you're the one configuring the tool, reviewing its outputs, and making final decisions based on AI recommendations, you may still be the deployer even though the EOR owns the platform. The EU AI Act looks at who exercises authority over the AI system's use, not who holds the software licence.

Consider a scenario where your EOR provides an AI screening tool that ranks candidates. If the EOR runs the tool and presents you with a shortlist, they're likely the deployer. But if you access the tool directly, set the screening criteria, and use the rankings to make hiring decisions, you're likely the deployer despite using the EOR's platform.

This distinction matters because deployer obligations include implementing human oversight measures, monitoring the system's operation, and suspending use if you identify risks. You can't delegate these obligations to your EOR through contract alone if you're the party actually deploying the system.

What should the EOR contract say?

Your EOR contract needs an AI responsibilities schedule that explicitly allocates EU AI Act duties between you and your EOR. Most current EOR agreements were drafted before the Act came into force and don't address AI compliance at all. That's a gap you need to close.

The schedule should specify which party is responsible for each AI-enabled HR workflow. For any AI system the EOR provides, the contract should clarify whether the EOR or the client is the deployer based on who has authority over the system's use. For AI systems you procure independently, the contract should confirm you retain deployer obligations.

Key provisions to include are documentation requirements, specifying who maintains records of AI system use and makes them available for regulatory inspection. Human oversight allocation matters too, clarifying who implements and monitors the required human review of AI outputs. Notification procedures should establish how each party informs the other of AI-related compliance concerns or incidents.

The contract should also address what happens when the EOR's local employment obligations intersect with your AI deployment obligations. In Germany, for example, works council consultation may be required before implementing AI monitoring tools. Your contract should clarify whether the EOR handles this consultation as part of their employment compliance role or whether you need to coordinate directly.

Teamed's approach is to include AI responsibilities as a standard schedule in every EOR master service agreement, with country-specific addenda that address local labour law requirements affecting AI deployment. Based on Teamed's work with mid-market companies across multiple EU jurisdictions, this structure prevents the assumption gaps that leave both parties exposed.

What if I use an EOR across multiple jurisdictions?

Multi-jurisdiction EOR arrangements multiply the complexity. The EU AI Act provides a baseline, but individual member states can layer additional requirements on top. German works council rights, French employee consultation obligations, and Dutch data protection interpretations all affect how you can deploy AI in employment contexts.

The challenge is that the same AI-enabled hiring process may trigger different local requirements in each country where you have EOR-employed workers. Your German team may require works council consultation before you implement an AI screening tool. Your French team may need individual employee notification. Your Dutch team may face stricter limits on automated decision-making under local GDPR interpretation.

A single workflow, many countries problem emerges. You need a governance model that standardises your AI-enabled hiring approach while accommodating country-specific constraints. That means documenting your AI deployment policies at the group level, then creating country-specific implementation guides that address local requirements.

Your EOR can help with the local employment law layer, but they can't manage your AI governance for you. Teamed's analysis of multi-country EOR programmes shows that companies operating in 5-15 EU countries typically need a dedicated AI compliance workstream that coordinates with their EOR's local employment expertise rather than delegating entirely to the EOR.

The practical solution is a GEMO approach, Global Employment Management and Operations, where a single provider manages your employment infrastructure across all jurisdictions while you maintain centralised AI governance. This prevents the fragmentation that occurs when different EOR providers in different countries give conflicting advice about AI compliance.

Can the EOR indemnify me?

Your EOR can contractually agree to indemnify you for losses arising from AI compliance failures. But an indemnity only shifts financial risk between the parties. It doesn't change who the regulator pursues for the underlying breach.

If you're the deployer under the EU AI Act and you fail to implement required human oversight, the regulator can pursue you directly. Your indemnity claim against the EOR is a separate commercial matter that doesn't affect your regulatory exposure. The regulator doesn't care about your contractual allocation of risk.

This is a crucial distinction that many mid-market companies miss. Contractual protections are valuable for managing commercial risk between you and your EOR. But they're not a substitute for actual compliance. You can't outsource your deployer obligations through contract any more than you can outsource your GDPR controller obligations.

What you can do is structure your EOR relationship so that responsibilities are clearly allocated and both parties have the operational capacity to meet their obligations. If your EOR is the deployer for certain AI-enabled functions they provide, they should have the compliance infrastructure to meet deployer obligations. If you're the deployer for AI systems you procure, you need your own compliance programme.

The indemnity becomes relevant when something goes wrong despite both parties' compliance efforts, or when one party's failure causes loss to the other. It's a backstop, not a compliance strategy.

What's the practical next step?

Start by mapping every AI system that touches your EU-employed workforce. Include recruitment tools, performance management systems, workforce analytics platforms, and any automated decision-making in HR processes. For each system, identify who has authority over its use, who configures it, who reviews its outputs, and who makes final decisions based on those outputs.

Then review your EOR contracts. Do they address AI compliance at all? Do they allocate deployer obligations between you and the EOR? Do they include country-specific provisions for jurisdictions with additional local requirements? If the answer to any of these is no, you have a gap to close.

For companies using EOR across multiple EU countries, consider whether your current provider structure supports coherent AI governance. Fragmented EOR relationships with different providers in different countries make it harder to implement consistent AI policies and maintain the documentation that regulators expect.

Teamed's GEMO framework provides one relationship across all employment models and jurisdictions, which simplifies AI governance by giving you a single point of coordination for the employment law layer while you maintain control of your AI deployment decisions. The graduation model means that as your needs evolve, whether from EOR to entity or from basic compliance to sophisticated AI governance, you don't need to rebuild your provider relationships.

If you'd like a second pair of eyes on that picture, Talk to an Expert. A named specialist will walk through your current EOR setup with you, show you where liability sits across each EU country, and help you decide what to tighten in your contracts and policies next. The honest answer, always.