India is home to over 5 million software developers, making it the largest pool of engineering talent outside the United States. For a US company, tapping into this market often feels like a necessity for growth. However, the traditional path of setting up a local private limited company can take months of paperwork and significant capital. Many businesses find themselves stuck, wondering if they can legally hire an Indian worker without the headache of an overseas entity.

The short answer is yes. A US business can hire in India without a local company by using specific structures like an Employer of Record (EOR) or by engaging independent contractors. These paths allow a company to get moving in weeks rather than months.

But moving fast does not mean moving without caution. India has strict tax rules and labor laws that do not care about a company's good intentions.

Misclassifying a worker or ignoring local social security contributions can lead to legal friction that stalls expansion plans before they even truly begin.

Note: While third-party hiring models help manage local employment, they do not automatically eliminate Permanent Establishment (PE) risk. PE is a complex tax status that depends on specific business activities and requires professional US–India tax advice.

This guide looks at how to navigate these waters safely. Readers will learn the difference between hiring a contractor and a full-time employee. The discussion covers how an EOR handles payroll and why "Permanent Establishment" is a term every CFO needs to understand.

It also explores the specific point when a company should stop using third parties and finally build its own Indian subsidiary. Navigating Indian compliance is a marathon, not a sprint.

Success depends on choosing a model that balances control with legal safety.

Can a US company hire an employee in India without a local entity?

Yes, a US company can hire in India without a local entity by using an Employer of Record (EOR) or hiring workers as independent contractors. An EOR acts as the legal employer on paper, handling local payroll, taxes, and compliance while the US company manages the worker's daily tasks.

Using an EOR is the most common way to hire full-time talent without the overhead of a subsidiary. The EOR already has an Indian entity, bank accounts, and registrations with the Ministry of Labour and Employment. This setup allows the US company to offer benefits like health insurance and provident fund contributions, which are expected by top-tier Indian professionals. It bridges the gap between being a foreign "client" and a legitimate "employer."

Alternatively, some companies choose the contractor route. This is simpler and requires less paperwork initially, as the worker is responsible for their own taxes. However, this path carries the risk of "misclassification." If a person works exclusively for one company, uses company equipment, and follows a fixed schedule, Indian authorities may view them as a de facto employee. In such cases, the US company could be liable for unpaid benefits and penalties.

Ultimately, the choice depends on the level of risk a business is willing to accept. While an EOR provides a layer of protection, it involves service fees and structured contracts. Companies must weigh these costs against the potential legal hurdles of direct contractor management or the high expense of setting up a full Indian private limited company.

What are the ways to hire in India?

US companies typically choose between three main paths: hiring independent contractors, using an Employer of Record (EOR), or establishing a local subsidiary. Each method offers different levels of legal protection, cost, and operational control over the Indian workforce.

1. Independent Contractors: The US company signs a service agreement directly with the individual. This is the fastest and cheapest method but offers the least control and highest risk of tax audits.
2. Employer of Record (EOR): A third-party service provider hires the worker on their local Indian payroll. The EOR manages all statutory compliance, including tax deductions (TDS) and social security.
3. Local Subsidiary: The US company registers an Indian entity (usually a Private Limited Company). This provides total control and is the best long-term move for large teams, though it requires significant time and legal maintenance.

How does an EOR differ from a contractor?

The primary difference lies in legal responsibility and benefit requirements. An EOR provides a formal employment contract under Indian law, including mandatory social security and tax withholding, whereas a contractor is a self-employed service provider responsible for their own taxes and insurance.

Who manages payroll and taxes in India?

In an EOR arrangement, the service provider manages all payroll tasks, including calculating salaries, withholding Tax Deducted at Source (TDS), and contributing to social security funds. If hiring a contractor, the US company pays a gross amount, and the contractor handles their own filings.

Payroll in India is not a simple "net pay" calculation. It involves several statutory components that change based on salary levels and employee headcount. For example, the Employees' Provident Fund (EPF) and Employees' State Insurance (ESI) have specific contribution rates that must be deposited with the government monthly. An EOR ensures these payments are made on time, shielding the US company from administrative errors.

When a US company reaches a certain scale, they may choose to bring payroll in-house by establishing an entity. At this stage, they would hire an Indian chartered accountant or a payroll processing firm to handle the monthly filings. Regardless of the method, failing to file TDS or social security contributions can result in heavy interest penalties and potential bars on future business activities in the country.

When should a US company establish an Indian subsidiary?

A US company should typically consider establishing an Indian subsidiary when their local headcount exceeds 15–20 employees or when they plan to sign local contracts and hold significant assets in India. A subsidiary offers better long-term cost efficiency compared to EOR fees.

There is a "tipping point" where the monthly fees paid to an EOR provider exceed the administrative costs of running a local company. Beyond the financial aspect, having a local entity signals a long-term commitment to the Indian market. This can be a major factor in recruiting high-level executive talent who may prefer the stability of a direct employment contract with a registered Indian company.

However, running a subsidiary comes with "compliance fatigue." The company must appoint local directors, hold annual general meetings, and file audited financial statements. For many startups, the EOR model serves as a perfect "bridge" for the first 12 to 24 months, allowing them to test the market before committing to the legal and financial burden of a full corporate setup.

Frequently Asked Questions

Is a US entity required to be registered in India to hire?

No, a US entity does not need to register a branch or office if they use an Employer of Record. The EOR uses its own existing Indian registration to employ the staff on behalf of the US client.

What is the risk of "Permanent Establishment" (PE)?

PE risk occurs when Indian tax authorities decide that a foreign company has a stable enough presence in India to justify taxing its global corporate profits. This is a fact-specific risk that depends on what the employees are doing (e.g., signing contracts vs. writing code) and requires specific tax advice.

Do Indian employees get US-style benefits?

While US companies can offer "perks" like stock options (subject to FEMA regulations), they must provide Indian statutory benefits first. This includes the Provident Fund, Gratuity (after 5 years of service), and specific leave entitlements mandated by the state where the employee resides.

Can I pay an Indian employee in USD?

It is generally difficult for an Indian resident to receive a regular salary in USD due to Foreign Exchange Management Act (FEMA) rules. Most compliant setups involve the US company sending USD to an EOR or entity, which then converts it and pays the employee in Indian Rupees (INR).

Disclaimer: This article is for informational purposes only and does not constitute legal or tax advice. Employment laws and tax treaties between the US and India are subject to change. Always consult with qualified legal and tax professionals before making international hiring decisions.

Can a US company hire an employee in India without a local entity?

Yes, US companies can legally hire Indian talent without a local entity by partnering with an Employer of Record (EOR). This model allows a US business to engage full-time staff through a third-party organization that handles all local payroll, benefits, and tax compliance under Indian labor laws.

Setting up a private limited company in India involves significant administrative overhead and capital requirements. For many US founders, this is an unnecessary hurdle. Instead, the Employer of Record acts as the legal employer on paper.

They take on the burden of generating payslips and filing social security contributions. The US company maintains the day-to-day management of the worker, effectively treating them as a member of the core team.

While an EOR provides the infrastructure, it is not a "set it and forget it" solution. I have seen companies rush into these agreements without realizing that professional legal and tax advice is still necessary to tailor the relationship. The EOR manages the mechanics of employment, but the US company must still define the roles and responsibilities to ensure they align with international tax treaties. I generally recommend that US HR teams treat an EOR as a strategic partner rather than just a software vendor.

Initial Considerations for US Operations Teams

Before moving forward, leadership must evaluate several factors to ensure the arrangement remains compliant and cost-effective. The following table highlights the primary focus areas for a successful start:

One common mistake is assuming that an EOR is a shield against all local risks. It is a powerful tool, but it does not automatically resolve the complexities of how the Indian government views your business presence. If an employee is given the power to sign contracts or negotiate deals on behalf of the US parent company, it can create unintended tax consequences.

This raises a specific concern that often catches US-based CFOs off guard. Even without a physical office or a local bank account, certain activities performed by your Indian staff can lead the tax authorities to decide that your company has a taxable "presence" in the country. This creates a situation where the US entity might be liable for corporate taxes in India, regardless of the employment model used.

What Is Permanent Establishment Risk in India?

Permanent Establishment (PE) is a tax concept where an Indian tax authority determines that a foreign company has a stable, ongoing business presence in India, making its global profits partially taxable locally. This status triggers corporate tax liabilities and complex filing requirements that most US startups are not prepared to handle.

A US company might believe it is operating purely from Delaware, but the Double Taxation Avoidance Agreement (DTAA) between the US and India defines specific thresholds for when a "virtual" presence becomes a physical tax obligation. When an employee’s actions cross these lines, the Indian government views the US entity as having a fixed place of business or a dependent agent within its borders.

I have seen founders ignore this until a tax notice arrives. By then, the financial damage is often done. The risk is not just about paying the standard corporate tax rate; it is about the administrative nightmare of an unplanned audit and the potential for significant back taxes and penalties on revenue that was never intended to be "Indian" income.

Common Triggers for Permanent Establishment

The dependent agent trigger is the most frequent trap for US companies. If an Indian hire has the authority to negotiate or conclude contracts on behalf of the US parent company, the tax authorities may argue that the US company is effectively conducting business in India through that individual. This often happens when a senior sales lead or executive is hired without strict guardrails on their decision-making power.

Another trigger involves the fixed place of business rule. If a US company provides a dedicated office space for its team-even a small coworking suite-it can be interpreted as a permanent site. While hiring through certain models helps structure local employment, PE is highly fact-specific. It requires a nuanced understanding of the specific activities the worker performs daily.

Financial and Legal Consequences of Accidental PE

The ramifications of an unintended PE finding are severe and immediate. Beyond the basic corporate tax on attributed profits, the US company faces interest on late payments and penalties for failing to register a local tax ID (PAN) or file annual returns. This can lead to a messy "double taxation" scenario where the same dollar of profit is taxed by both the IRS and the Indian Income Tax Department, with limited relief available if the paperwork wasn't handled correctly from day one.

• Tax Liability: Direct corporate tax on profits attributed to the Indian "branch."
• Compliance Backlog: Requirement to reconstruct years of financial records for Indian filing.
• Reputational Risk: Potential blacklisting or difficulties in future entity registration.
• Audit Exposure: Increased scrutiny of all inter-company transactions and transfer pricing.

Frequently Asked Questions

Founders must realize that PE risk is a spectrum, not a binary switch. Engaging a developer to write code is generally lower risk than hiring a Business Development Manager with signing authority. Success depends on aligning the worker's role with the legal structure chosen to support them.

How Can a US Company Hire in India Compliantly?

A US company can hire Indian talent by using an Employer of Record (EOR), engaging independent contractors, or establishing a local subsidiary. Each path balances speed, operational control, and tax exposure differently, requiring founders to choose based on their long-term growth plans and risk tolerance.

The choice between these models is rarely about finding a "perfect" solution. It is about choosing which trade-offs a business can live with. For many startups, the decision starts with a simple question: how much administrative weight is the team ready to carry? The answer usually points toward one of three distinct legal frameworks.

The Employer of Record (EOR) Model

An EOR acts as the legal employer on the ground. While the US company manages the worker's daily tasks and performance, the EOR takes on the burden of payroll, local tax filings, and mandatory social security contributions. This model is often the fastest route to market for teams that do not want to manage the complexities of Indian labor laws directly.

It is important to distinguish an EOR from a Professional Employer Organization (PEO). In a domestic US context, a PEO shares employment responsibilities through a co-employment agreement. Internationally, however, an EOR is the sole employer of record, which provides a layer of separation between the US entity and the Indian workforce. Fees for these services typically range from $400 to $800 per employee per month, depending on the complexity of the benefits package provided.

The Independent Contractor Path

Engaging contractors offers the highest level of flexibility and the lowest immediate overhead. The US company pays the individual directly, and the worker is responsible for their own taxes and insurance. However, this path is fraught with classification risk. If a worker performs the same duties as a full-time employee, the Indian government may reclassify them, leading to significant back-tax liabilities.

The Wholly-Owned Subsidiary

Establishing a local entity provides the highest level of control but requires the most significant investment. This involves registering a private limited company in India, appointing local directors, and maintaining a physical office. This path is generally reserved for companies committed to a large-scale, long-term presence in the region.

Choosing the wrong path can lead to more than just administrative headaches; it often triggers the very tax complexities that founders work so hard to avoid. The line between a "service provider" and a "de facto employee" is thin, and crossing it unintentionally changes everything about a company's legal obligations in India.

How Do You Distinguish Between an Employee and a Contractor in India?

Indian labor law distinguishes employees from contractors based on the level of control a company exerts over the worker's daily tasks and how integrated that individual is into the core business operations. While a contract might label someone an independent worker, Indian courts look past the document to the actual nature of the relationship.

Deciding between these two paths is the most high-stakes choice a US founder makes when entering the Indian market. Choosing the contractor route for a full-time role feels like a shortcut, but it often creates a "hidden" employment relationship. If the worker performs core functions, uses company-provided hardware, and follows a strict schedule, Indian authorities likely view them as an employee regardless of what the signed agreement says.

To determine the true status of a worker, Indian legal precedents rely on two primary benchmarks: the control test and the integration test. I have seen companies ignore these and face heavy demands for back-dated benefits years later.

The Control and Integration Tests

The control test examines who dictates the "how, when, and where" of the work. If a US manager sets specific working hours, provides a laptop, and requires the worker to follow internal disciplinary codes, the worker is likely an employee. Contractors, by contrast, should generally use their own tools and maintain autonomy over their methodology.

The integration test looks at whether the person is "part and parcel" of the organization. If the worker is a lead developer building the company's primary software product, they are integral to the business. If they are a specialized consultant providing a one-off security audit, they are more likely a true contractor. Mislabeling a core team member as a contractor is a frequent trap that triggers significant liabilities.

Risks of Misclassification in India

The financial fallout of getting this wrong is immediate and cumulative. When a worker is reclassified as an employee, the US company becomes liable for years of unpaid statutory contributions and potential litigation.

Courts in India are traditionally pro-labor. A disgruntled contractor can file a claim asserting they were denied the protections of the Industrial Disputes Act. If successful, the company may be forced to pay gratuity-usually reserved for long-term employees-and provide the same job security as a permanent hire. These disputes often arise during termination, turning a simple parting of ways into a multi-year legal battle.

Establishing a compliant relationship requires more than just a well-drafted contract; it requires a payroll structure that aligns with the worker's actual daily reality. This brings us to the complex web of mandatory deductions and social security schemes that apply the moment a worker is recognized as an employee under Indian law.

What Are the Mandatory Payroll Obligations for Indian Employees?

Indian payroll involves withholding income tax (TDS), contributing to social security schemes like EPF and ESI, and accounting for long-term benefits such as gratuity. These statutory requirements are strictly regulated and must be processed according to the Indian financial year, which runs from April 1 to March 31.

Calculate the net pay for an Indian worker by first deducting Tax Deducted at Source (TDS). This is the mandatory income tax withholding that employers must remit to the government on behalf of the employee. Unlike the US system, where tax filings are often annual, Indian compliance requires monthly deposits and quarterly filings to ensure the worker's tax credit is updated in real-time.

Social security in India is primarily driven by the Employee Provident Fund (EPF). For most employees, both the employer and the employee contribute 12% of the basic wages toward this retirement savings scheme. While it provides a safety net for the worker, it adds a significant overhead to the gross salary that US companies must factor into their total cost of employment.

Key Statutory Contributions and Benefits

Beyond retirement savings, the Employee State Insurance (ESI) provides medical and sickness benefits. This is mandatory for employees earning up to INR 21,000 per month. The employer contributes 3.25%, while the employee contributes 0.75% of the wages. If a worker's salary exceeds this threshold, they generally move out of the ESI net, and companies often substitute this with private group medical insurance.

The Payment of Gratuity Act creates a long-term liability for the employer. Gratuity is a statutory benefit payable to employees who have completed at least five years of continuous service. It is calculated as 15 days of the last drawn salary for every completed year of service. I have seen many US startups ignore this on their balance sheets, only to face a significant "catch-up" payment when a long-term hire eventually departs.

Managing Compliance Timelines

State-level taxes also apply, such as Professional Tax, which is levied by various state governments and capped at INR 2,500 per year. Additionally, some states require contributions to the Labour Welfare Fund (LWF), a small nominal fee paid semi-annually or annually to support worker welfare programs. Missing these small deadlines often triggers disproportionate scrutiny from local labor inspectors.

Managing these moving parts is the primary reason US companies lean on an EOR. The EOR handles the registration with the various departments, calculates the monthly cycles, and issues the mandatory "Form 16" tax certificates. Since an EOR's ability to handle these items directly impacts the legal safety of the hire, evaluating their specific local expertise becomes the next logical step for any expanding business.

Frequently Asked Questions

• Is a US entity required to run payroll in India? No, a US company can use an EOR to handle all local payroll and tax filings without a local subsidiary.
• Who manages the monthly payroll? If using an EOR, the provider manages the entire cycle; if hiring contractors, the US company pays the invoice directly, though the contractor is responsible for their own taxes.
• When should I move from an EOR to a subsidiary? Most companies consider a private limited company once the headcount reaches a level where EOR fees exceed the cost of maintaining a local legal and accounting team.

How Do You Evaluate an India EOR Partner?

A US company should evaluate an India EOR based on their local entity ownership, transparent pricing structures, and in-house compliance expertise. Selecting a partner with a direct presence in India minimizes legal layers and ensures faster response times during the typical two-to-four-week onboarding process.

Four out of five global expansion failures stem from poor local execution rather than strategy. When a business hires in India, it isn't just buying software; it is entering a legal partnership. Some providers act as aggregators, subcontracting the actual employment to local third parties. This creates a "telephone game" effect where sensitive payroll data and legal queries pass through multiple hands, increasing the risk of errors and data breaches.

Direct entity ownership is the primary indicator of a stable EOR. A provider that owns its Indian subsidiary has a vested interest in maintaining a clean record with the Ministry of Corporate Affairs. This direct link allows for tighter control over data security and ensures the person handling an employee's tax query actually works for the company being paid. Choosing a generalist who manages fifty countries may seem convenient, but they often lack the "boots on the ground" needed to handle specific Indian labor disputes or sudden regulatory shifts.

1. Verify Local Entity Ownership - Ask the provider if they own the Indian private limited company that will appear on the employee's pay stub. If they use a partner, the US company faces higher costs and less control over the employee experience.
2. Audit the Pricing Model - Compare whether the EOR charges a flat fee per employee or a percentage of the gross salary. Flat fees are generally more predictable for budget planning as they do not penalize the employer for giving the worker a raise.
3. Test Support Responsiveness - Send a complex query regarding local labor laws or Form 16 issuance. A delay of more than 24 hours during the sales process is a red flag for how they will treat an employee's urgent payroll issue later.
4. Review Data Security Standards - Ensure the provider is SOC2 or ISO 27001 compliant. Since the EOR will handle sensitive Permanent Account Numbers (PAN) and bank details, their digital infrastructure must be airtight.
5. Confirm Onboarding Timelines - Request a detailed schedule for the 2-4 week setup period. This should include specific dates for contract signing, document collection, and the first payroll run to avoid missing statutory deposit deadlines.

Transparent pricing remains a significant hurdle in the EOR industry. Hidden "onboarding fees" or "termination charges" can inflate a $600 monthly fee into something much larger. A reputable partner provides an itemized breakdown of every cost before any contracts are signed. This clarity is vital because EOR fees typically range from $400 to $800 per employee per month, and unexpected add-ons can derail a department's annual budget.

Engagement doesn't end at the hire; the EOR must be equipped to handle the full lifecycle of the worker. This includes managing local labor disputes or navigating the legal requirements of a performance improvement plan. A partner who only offers a "self-service portal" without access to a local HR expert leaves the US company vulnerable when complex human elements of the workplace inevitably arise.

Conclusion

A US company can hire in India without a local entity by utilizing an Employer of Record (EOR) or hiring independent contractors, provided they navigate tax and labor laws carefully.

Hiring in India requires a shift from US-centric thinking to a localized compliance mindset. While the talent pool is vast, the legal framework is rigid. A US company does not need a local office to start, but they must ensure every worker is classified correctly from day one. Missteps in classification or tax withholding often lead to complications that far outweigh the initial savings of a DIY approach.

Success depends on matching the hiring model to the long-term business goal. Short-term projects might suit contractors, while building a dedicated team often warrants an EOR to manage statutory benefits like the Provident Fund and Gratuity. The reader should remember that compliance is a continuous process, not a one-time setup. As the team grows, the transition to a full Indian subsidiary becomes a matter of when, not if.

Key Takeaways for US Employers

• EORs provide a structural buffer: An Employer of Record acts as the legal employer in India, managing payroll and benefits, which helps the US company avoid the immediate need for a local Tax ID and bank account.
• Permanent Establishment (PE) is fact-specific: Using an EOR does not automatically eliminate PE risk. Tax authorities look at the nature of the work and decision-making authority; US-India tax advice is essential to evaluate specific risks.
• Statutory benefits are non-negotiable: Indian labor laws require specific contributions to the Employees' Provident Fund (EPF) and payment of Gratuity after five years of service for eligible employees.
• Contractor risks are high: Hiring "contractors" who function as full-time employees can lead to legal claims for benefits and significant back-tax liabilities if the Indian government reclassifies the relationship.

Pro tip: Always verify that a chosen EOR partner has a valid Indian recruitment license and a physical presence in the state where the employees reside to ensure local compliance.

Next Steps to Take Today

1. Review the specific job descriptions for Indian candidates to determine if their roles involve revenue-generating activities that could trigger tax nexus.
2. Request a sample breakdown of "Cost to Company" (CTC) from an India hiring specialist to understand how local social security and taxes impact the total budget.

The right partner makes the Indian market accessible without the burden of immediate entity formation.

Frequently Asked Questions

Is a US entity required to register in India to hire?

No, a US entity is not required to register a local branch or subsidiary if they use an Employer of Record (EOR). The EOR serves as the local legal entity for employment purposes, holding the necessary registrations to run payroll and pay taxes. However, if the US company intends to engage in direct trade or sign local contracts, a subsidiary may eventually become necessary.

What is the difference between an EOR and a contractor?

An EOR hires an individual as a full-time employee under Indian labor law, whereas a contractor is a self-employed service provider. EOR employees receive statutory benefits like health insurance and retirement contributions. Contractors manage their own taxes and do not receive benefits, but the US company faces higher legal risks if the contractor is treated like a de facto employee.

Who manages the day-to-day payroll and taxes?

In an EOR model, the EOR provider manages all payroll calculations, tax withholdings (TDS), and social security filings. The US company pays a single invoice to the EOR, which then distributes salaries to the Indian workers in Rupees. If hiring contractors, the US company typically pays the individual directly, and the individual is responsible for their own GST and income tax filings.

When should a US company establish a subsidiary in India?

Most companies consider establishing a subsidiary when their Indian headcount exceeds 15 to 20 employees or when they require a permanent physical office. At this scale, the administrative costs of an EOR may begin to exceed the costs of operating a private limited company. A subsidiary also provides the US parent company with direct control over all intellectual property and local business operations.

Disclaimer: This article is for informational purposes only and does not constitute legal or tax advice. Readers should consult with qualified legal and tax professionals in both the US and India before making hiring decisions.

Related India Hiring Resources

• How to Hire Employees in India Without Setting Up a Company
• India Employment Laws for Foreign Companies
• Contractor vs Full-Time Employee in India
• PEO vs EOR Services in India
• Employer of Record India Cost
• Payroll Compliance in India for Foreign Employers