US Employees Relocating to India: Payroll & Tax Setup Guide

Relocating a US employee to India means rebuilding their payroll and tax setup from scratch within 30 to 60 days. Once the employee crosses 182 days in India during the financial year, their salary becomes India-sourced, US payroll providers can no longer legally process their pay, and the US parent risks triggering Permanent Establishment (PE) status.

For most companies, the cleanest path is to terminate the US employment and re-onboard the employee through an India-based Employer of Record (EOR). This guide is the end-to-end runbook: residency rules, payroll options, US and Indian tax forms, DTAA mechanics, the totalization gap, and a 90-60-30-day timeline.

Why is relocating a US employee to India different from hiring locally?

Relocating a US employee to India is a transition problem, not a hiring problem. The employee already exists on US payroll with vested benefits, equity grants, a 401(k) balance, and a fixed compensation structure. Hiring locally in India means a clean start. Relocation means rewiring an active employment relationship across two tax jurisdictions, two social security systems, and two sets of statutory contributions, often inside a 30 to 60 day window.

This shift is accelerating as India now hosts 45% of the global GCC talent base, making cross-border employee relocation and India payroll restructuring increasingly common for US companies expanding engineering, product, and operations teams (Source: Wisemonk India IT Services Report 2026)

Four relocation scenarios show up most often, and each one triggers a different setup path:

• US citizen on overseas assignment. Stays a US tax resident on worldwide income for life. DTAA claims and shadow payroll often apply.
• Indian-origin employee repatriating (NRI returning home). Often qualifies for RNOR status, which gives a two-year window of relief on foreign-sourced income.
• Green card holder making a permanent move. Same worldwide income exposure as a US citizen until the green card is formally surrendered.
• Remote-first lifestyle relocation. Employee just wants to move. Usually the most paperwork-light scenario but still triggers the full payroll rebuild once 182 days pass.

The setup playbook for a returning Indian engineer with NRO accounts and an existing PAN looks nothing like the playbook for a US citizen on a two-year assignment. Pinning down the scenario is the first decision before any payroll setup work begins.

What determines whether the employee owes tax in India, the US, or both?

Tax residency is the trigger. Once a relocating employee crosses 182 days of physical presence in India during the financial year (April 1 to March 31), they become an Indian tax resident, and India gains the right to tax their salary. US citizens and green card holders, separately, never stop being US tax residents on worldwide income unless they formally expatriate or surrender the green card. So most relocating employees end up filing in both countries. The DTAA decides which country gets which tax dollar.

India runs a secondary residency test that catches more people than the headline 182-day rule: 60 days in India during the financial year, combined with 365 days across the prior four years, also makes the employee a resident. For most repatriating engineers and US citizens on a multi-year assignment, the secondary test is usually satisfied long before the headline one matters.

Once an employee qualifies as an Indian resident, India splits them further into three categories:

The DTAA tiebreakers (permanent home, center of vital interests, habitual abode, citizenship) only kick in when both countries claim the same income under their domestic rules. For salaried employees physically working from India, India almost always wins the source claim.

Check out: Tax Compliance in India: Comprehensive Guide 2026

How does RNOR status help returning Indian-origin employees?

RNOR is the most underused tool in cross-border tax planning. A returning NRI usually qualifies for RNOR for two financial years after coming back, and during that window, India does not tax foreign-sourced income (US brokerage interest, US dividends, US rental income). Only Indian salary and Indian-source income are taxable. For an Indian-origin employee with a meaningful US investment portfolio, the RNOR window is worth real money. The employee should claim RNOR status explicitly when filing ITR-2, since the default classification by Indian authorities is often ROR.

What payroll setup options does a US company have for a relocating employee?

There are four real options, and the right choice depends almost entirely on headcount and how long the relocation lasts. For a single relocating employee on a permanent move, an Employer of Record (EOR) wins on cost, speed, and risk. For 15 to 20+ India-based employees with multi-year horizons, an entity starts to pay back. The other two options (keeping the employee on US payroll, or converting them to an Indian contractor) look easy upfront but create disproportionate compliance and PE risk.

Here's the comparison most finance leads need to put in front of their CFO:

A few practical notes on each option:

• Keep on US payroll. Stops being legal once the employee is an Indian tax resident. US payroll systems cannot withhold Indian TDS, contribute to Employees' Provident Fund, or remit Employee State Insurance. Some companies run a shadow payroll for tax equalization purposes, but the actual employment must move to an Indian structure.
• Indian contractor. Works for a 3 to 6 month transitional engagement. Beyond that, the relationship usually fails the misclassification test under Indian labor law: fixed hours, sole client, equipment provided, performance reviews. The employee also loses statutory benefits like Provident Fund and gratuity, which often kills retention.
• EOR. The EOR becomes the legal Indian employer, handles all statutory contributions, runs Indian payroll in INR, and firewalls the US parent from PE risk. The US company directs the day-to-day work.
• Indian subsidiary. Full control, owned employees, but the registration, filings, statutory audits, and ongoing payroll compliance carry real overhead. Justified when committed Indian headcount makes the fixed cost reasonable.

For a single relocating employee, the EOR route is almost always the answer. The math gets interesting only at scale.

What is permanent establishment risk and how does relocation trigger it?

Permanent establishment (PE) risk is the single biggest reason a US company cannot just keep a relocated employee on US payroll. PE is created when a foreign company has a "fixed place of business" or a "dependent agent" in India through which it carries on business.

A relocated US employee performing core revenue activity from India, signing contracts, managing customer relationships, or making key decisions, can establish PE for the entire US parent. The tax consequence is that India can claim tax on the share of the US company's global profits attributable to Indian operations, at corporate rates of around 35 to 40 percent.

Across 300+ global companies and 2,000+ employees we've onboarded into India, with $20M+ in annual payroll moving through our books, here's what we've consistently seen on PE risk: it almost never gets caught early, and almost always gets caught during a Series B or later funding round when due diligence pulls the thread.

The activities that escalate PE risk fastest are the ones that look most like normal startup work:

• Sales and contract signing. A relocated AE or solutions engineer closing US customers from Bangalore is a textbook dependent-agent PE.
• Key managerial decisions. A founder, VP Engineering, or department head running the function from India creates a place-of-management PE.
• Customer-facing delivery. A customer success lead managing the US book of business from India can also trigger PE depending on contract authority.

Engineering work performed for an internal product, with no external customer contact, sits at the lowest end of the PE risk spectrum. But it still carries risk if the employee is making architectural or product decisions that drive revenue.

An EOR firewalls all of this. The EOR becomes the legal Indian employer, the US company is contractually a customer of the EOR, and the dependent-agent and fixed-place tests both fail by design. PE risk drops from material to negligible.

Which US tax forms does the relocating employee need to file?

A relocating US citizen or green card holder keeps filing US taxes for life, but the form set changes the moment they become an Indian tax resident. The headline forms are Form 1040 (annual filing on worldwide income), Form 8233 (stops US tax withholding once the employee is treaty-resident in India), Form 8938 and FinCEN 114 (FBAR for foreign accounts), Form 8833 (treaty-based position disclosure), and Form 1116 or 2555 (Foreign Tax Credit or Foreign Earned Income Exclusion).

Here's the forms map by phase:

• Pre-relocation. Update Form W-4 and gather Form 8233 documentation so US payroll taxes can be stopped on day one of Indian residency.
• Year of relocation. A dual-status return on Form 1040 plus Form 1040-NR may apply. Form 8233 goes to the US employer to stop tax withholding once treaty residency is claimed.
• Ongoing years. Form 1040 every April on worldwide income. Form 1116 for Foreign Tax Credit, or Form 2555 for the Foreign Earned Income Exclusion. Form 8833 to disclose the treaty position.
• Foreign account disclosures. Form 8938 if foreign financial assets exceed $200,000 at year-end (single filers abroad). FBAR if any foreign account hits $10,000 at any point in the year.

One nuance worth flagging: Form 8938 does not satisfy FBAR, and FBAR does not satisfy 8938. They are separate filings with separate thresholds and separate penalties.

In steady state, most employees only touch four of these annually. The complexity sits in the relocation year itself.

See: W9 vs. W2: Which IRS Form Should You Use? (2026 Guide)

Which Indian tax forms and registrations does the employee need?

The Indian side is shorter than the US side, but every step is gating: nothing else starts until these are in place. The relocating employee needs a Permanent Account Number (PAN) before any salary payments can be processed, ITR-2 as the annual return, Schedule FA for foreign asset disclosure once they qualify as ROR, and Form 67 to claim credit for US tax already paid. Advance tax is also due quarterly if Indian income tax owed exceeds ₹10,000.

Here's the registration and filings map:

• PAN. Required for salary, a local bank account, any return, or to pay tax. Returning Indian-origin employees usually have one; foreign nationals apply via Form 49AA.
• Aadhaar-PAN linkage. Mandatory for filing income tax in India.
• ITR-2. Annual return for salaried individuals with foreign assets or capital gains. Filed by July 31.
• Schedule FA. Discloses foreign accounts, brokerage holdings, RSUs, and ESPP shares. Mandatory for ROR, not for RNOR.
• Form 67. Filed before the ITR to claim Foreign Tax Credit on US tax paid. Skipping it means losing the credit.
• Advance tax. Quarterly payments if Indian tax owed crosses ₹10,000. Misses trigger Section 234B and 234C interest.

Need a deeper view of the Indian payroll layer? See our guides on payroll tax in India and payroll compliance in India.

For employees on EOR payroll, the EOR handles PAN, the local bank account, TDS deductions, and Employees' Provident Fund Organisation registration. The employee owns ITR-2, Schedule FA, Form 67, and advance tax.

How does the US-India DTAA prevent double taxation in practice?

The Double Taxation Avoidance Agreement between the US and India does not stop the relocating employee from filing in both countries. It only stops the same dollar of income from being taxed twice. The treaty defines source rules (which country has the first claim on each income type) and gives the taxpayer a Foreign Tax Credit mechanism to offset what was paid abroad.

For salary earned for work physically performed in India, India is the source country and gets the first claim. The US, for its citizens and green card holders, taxes the same income but allows the Indian tax paid to be credited against the US bill on Form 1116.

The practical claim sequence runs in two directions:

• Stop US withholding upfront. The employee files Form 8233 with the US employer, who then reports payments on Form 1042-S instead of W-2. This avoids US payroll taxes being deducted on India-sourced salary in the first place.
• Claim Indian credit for any US tax that was withheld. If US tax got deducted before Form 8233 was filed, the employee files Form 67 with the Indian return to claim the credit and recover it.

The treaty also runs tiebreaker articles (permanent home, center of vital interests, habitual abode, citizenship) for cases where both countries claim the employee as a tax resident. For most salaried employees physically based in India, the tiebreaker resolves in India's favor.

For a deeper look, read the full guides on legal requirements for hiring in India, payroll compliance in India, and HR policies in India.

The DTAA stops double tax. It does not stop double filing.

Why does the missing US-India totalization agreement matter?

The US and India do not have a totalization agreement in force. That single missing treaty is the biggest hidden cost in most relocations, and almost no top-ranking guide treats it seriously. A totalization agreement coordinates social security contributions between two countries so the employee and employer do not pay into both systems on the same wages. Without one, a relocating US employee can owe US FICA (7.65 percent employee plus 7.65 percent employer) AND Indian Employees' Provident Fund contributions (12 percent each side) on the same salary.

After managing $20M+ in annual payroll for 300+ companies and 2,000+ employees across India, we've watched this exact line item catch finance teams off guard.

The cost depends on the payroll structure:

• Kept on US payroll. FICA is withheld in the US, and EPF contributions kick in once treaty residency applies. Worst case, both run in parallel.
• EOR-employed. US employment ends, FICA stops, and only Indian Provident Fund applies. Cleanest structure.
• Indian contractor. No EPF, but US self-employment tax (~15.3 percent) usually applies for US citizens.

A worked example on a $120,000 salary: staying on US payroll while resident in India means roughly $9,180 in FICA plus $14,400 in EPF, a duplicated employer burden near $23,500 annually. The EOR route cuts FICA out and leaves only the EPF side. This is the line item rarely modeled in relocation calculators.

How do FBAR and FATCA reporting work for a US employee in India?

FBAR and FATCA are the two foreign account disclosure regimes a relocating US employee has to file annually, and they are completely separate. FBAR (FinCEN Form 114) is triggered when the aggregate balance across all foreign financial accounts exceeds $10,000 at any point in the calendar year. FATCA (Form 8938) kicks in at much higher thresholds: $200,000 at year-end or $300,000 at any time during the year for unmarried filers living abroad. Indian salary accounts, NRE/NRO bank accounts, mutual funds, and brokerage holdings all count toward both.

The mechanics most filers get wrong:

• One does not satisfy the other. Filing FBAR does not satisfy Form 8938, and vice versa. They go to different agencies (FinCEN and the IRS) with different penalty regimes.
• Indian mutual funds are PFICs. Indian equity and debt mutual funds usually qualify as Passive Foreign Investment Companies under US tax rules, which triggers Form 8621 and punitive taxation. Most relocated employees are better off avoiding Indian mutual funds entirely and holding US-domiciled equivalents.
• Streamlined Filing Compliance Procedures. If FBAR or 8938 was missed in past years and the failure was non-willful, the IRS Streamlined program lets the employee come into compliance without criminal penalty.

Indian banks now report US-person accounts directly to the IRS under FATCA inter-governmental agreements. Hiding accounts is no longer feasible. The right move is to file accurately every year and treat both regimes as standard annual housekeeping.

What is the right pre-relocation timeline for payroll and tax setup?

A clean relocation needs a 90-day runway. Compressed timelines work but they cost more, carry higher error risk, and almost always leave one or two filings late. The runbook below is what we run for clients with three months of notice; the 60-day and 30-day variants drop steps in priority order.

Here's the day-by-day, working backwards from the move date:

• 90 days before. Confirm the relocation scenario (US citizen, NRI returning, green card holder, lifestyle move). Decide payroll structure (EOR vs entity vs contractor). Model total cost across both regimes, including the FICA-plus-EPF gap. Confirm the financial year math on the 182-day test so residency change is timed deliberately.
• 60 days before. Start EOR onboarding or entity registration. Draft the Indian-law-compliant employment contract. Plan equity and RSU treatment for vesting events post-move. Confirm Foreigners Regional Registration Office (FRRO) requirements for non-Indian-citizen relocations.
• 30 days before. Apply for PAN. Open the local bank account for INR salary deposits. Prepare Form 8233 for the US withholding stop. Brief the employee on advance tax, Form 67 for FTC, and Schedule FA. Decide the health insurance bridge between US group plan and Indian benefits.
• Day 1 in India. First Indian payroll runs. Employees' Provident Fund and Employee State Insurance deductions begin. US employment formally ends.
• First 90 days post-move. File pending US disclosures. Register with FRRO within 14 days for long-stay visa holders. Confirm FEMA salary repatriation compliance.

Compressed timelines force trade-offs. Skipping the 90-day cost modeling step is the most common mistake: the FICA-plus-EPF gap surfaces after the first payroll runs and the budget shifts mid-quarter.

How should equity, RSUs, and bonuses be handled during relocation?

Equity is the most common blind spot in relocation planning, and the rules get complicated fast. The general principle: vesting income gets allocated between US and India source based on workdays in each country during the vesting period. An RSU grant that vested over four years (two in the US, two in India) is roughly half US-source and half India-source at vest. Both countries can tax their share, and Form 67 in India plus Form 1116 in the US prevent the same dollar from being taxed twice.

A few practical points:

• RSUs vesting after the move. Allocate by workday split during the vesting period. The Indian portion gets taxed as perquisite income at vest under Indian law.
• ESPP discounts. The discount portion is treated as perquisite income in India at the time of vesting or purchase, depending on plan structure.
• Capital gains on US securities. Once the employee is an Indian resident (ROR), capital gains on sold US stock are taxable in India under Indian residency rules, with credit for any US tax already paid.

For employees with material equity, coordinated tax advice (a US CPA plus an Indian CA) is worth the fee. The dollars at stake usually justify the spend.

How does Wisemonk simplify payroll and tax setup?

Wisemonk is an India-native EOR built for global companies hiring and relocating employees into India, including US companies whose existing employee just moved home and needs a payroll rebuild within 30 to 60 days. We're not a global EOR with India as one of 90 countries.

We've handled this transition for 300+ global companies, 2,000+ employees, and $20M+ in processed payroll, so the setup playbook below is what we run, not what we recommend in theory.

What this looks like for a US founder, CFO, or Head of People relocating an employee:

• End-to-end transition, not just payroll. PAN application, local bank account, employment contract drafting under Indian law, EPFO/ESIC registrations, and TDS calibration from day one.
• PE risk firewalled by design. Wisemonk becomes the legal Indian employer, breaking the dependent-agent and fixed-place-of-business tests for the US parent.
• DTAA coordination across both sides. We coordinate the Form 8233 process with your US payroll team and support Form 67 filings on the Indian return.
• Equity continuity preserved. US RSUs, ESPP, and option grants keep vesting through the US parent. We handle the perquisite tax treatment in India.
• Transparent USD-denominated salaries. Salaries can stay denominated in USD with FX-transparent INR conversion at each pay run, so the employee's take-home does not silently shift with currency moves.

If you have a US employee relocating to India and the timeline is tight, this is built for you.

Voices from Our Clients

"Process was professional & very smooth. We've worked with Wisemonk to source developers in India and it's worked incredibly well for us. We are very pleased with the talent of the developers and the Wisemonk process was professional and very smooth. We highly recommend using Wisemonk for talent sourcing!" - Gear Fisher, Co-founder at Onform, USA

"I'm very Happy that I discovered Wisemonk. They have been a pure pleasure to work with, and their attention to detail is impressive. They helped us understand their pricing model, find top-qualified individuals, interview them, and then onboard them. I gave them criteria for the type of people we sought, and they delivered. The individuals they were able to find have been some of the best engineers I have ever worked with. I recommend Wisemonk to anyone who is in need of staffing assistance." - Dan Sampson, Head of Engineering at Cobu, USA