Employer of Record in India: A Manufacturer Decision Memo

Treat an employer of record India arrangement as an employment-administration workstream. Do not treat it as proof that a manufacturer's product, tax, establishment, regulatory, or site obligations are covered. In the decision memo, separate the workstreams. Give each one an owner, evidence, and an open question. Compare providers by the employment-administration scope in the proposed contract. Do not rely on a promise of full compliance. Obtain fact-specific professional advice for legal or tax conclusions. Do not infer that an EOR eliminates legal exposure.

Official starting point only, not a citation supporting any proposition in this memo: Ministry of Labour and Employment homepage.

If the EOR question sits inside a wider India entry decision, compare the evidence standard in this market intelligence report sample before treating a provider memo or quote as decision-grade research.

What does Employer of Record mean in this memo?

In this memo, "Employer of Record" is a working label. It describes a provider proposed to administer the employment relationship. The manufacturer still directs the person's work. That wording defines the commercial scope assessed here. It does not assert that Indian law recognizes one universal EOR structure. Confirm the arrangement against the facts before relying on a legal or employment conclusion.

The decision is therefore not "EOR or compliance." Ask which party is proposed to perform each task. Record the evidence for that allocation. Then list the obligations that remain outside the employment-administration contract.

Responsibility boundary for a manufacturer

The table is a decision-record template, not a statement of Indian legal allocation. Obtain fact-specific advice before treating any row as a legal conclusion.

Workstream	Question for the decision memo	Evidence to request	Boundary to record
Employment administration	Who is proposed to issue employment documents, run payroll, make employment filings, and administer stated contributions and benefits?	Proposed contract, provider registration claims, sample employment document, sample payroll output, and sample invoice	Record only the tasks and liabilities the contract states. Do not infer product, tax, establishment, regulatory, or site coverage.
Product obligations	Which obligations has the manufacturer identified for the product involved?	Product-specific assessment and the records identified in that assessment	Keep product conclusions outside the employment-administration workstream unless the contract expressly states otherwise and the conclusion is independently verified.
Tax and establishment	What activities will the India personnel perform, and what authority will they have in negotiations and contracts?	Written description of the activities and contract-signing authority, plus a fact-specific tax assessment	Do not use an EOR contract or vendor description as a tax or permanent-establishment conclusion.
Regulatory permissions	Which permissions are being assessed for the planned activity?	Activity-specific assessment and the resulting authority records	Do not treat employment administration as evidence that a regulatory permission exists.
Site operations	Will the plan involve a factory, warehouse, inventory, machinery, imports, or another operating site?	Site and activity description plus the records identified by the relevant assessment	Keep site ownership and operating responsibilities separate from the employment-administration scope.

Questions to settle before comparing EOR companies in India

• Which roles are proposed, where will the people work, and who will direct their day-to-day work?
• Will any India-based person negotiate or sign contracts for the manufacturer?
• Does the plan involve a factory, warehouse, inventory, machinery, imports, or another operating site?
• Which product, tax, establishment, regulatory, and site questions remain unresolved?
• Who owns each unresolved question, and what evidence will close it?

These are scoping questions, not legal tests. Use the answers to brief the appropriate adviser and the proposed provider.

What questions should go to the provider and advisers?

Send the same written fact pattern to every provider under review. This makes the answers easier to compare. It also helps an adviser see where the provider's proposed scope ends. The questions below are prompts for diligence. They do not state what the law requires.

Questions for the provider:

• Which legal entity would sign the service contract, and which entity would appear on the proposed employment documents?
• Which tasks would that entity perform before the person starts work, during routine administration, and when the arrangement ends?
• Which tasks would remain with the manufacturer, its other providers, or its advisers?
• Who would answer worker questions about employment documents, payroll outputs, stated benefits, or provider invoices?
• What source document would the provider use for the person's role, location, reporting line, pay inputs, leave inputs, and work status?
• How would the provider document a change in role, manager, authority, duties, work location, or travel pattern?
• Which sample outputs can the provider share for review before a decision is made?
• Which contract terms describe exclusions, error handling, escalation, records, confidentiality, and the end of service?

Questions for legal or employment advisers:

• Which facts about the proposed worker, role, location, provider, and contracting parties need separate review?
• Which provider claims should be tested against source records rather than accepted as contract language?
• Which conclusions are specific to this worker or arrangement and should not be copied to another hire?
• What facts would trigger a fresh review of the employment-administration scope?
• Which open points should be resolved before signature, and which can remain as tracked decisions?

Questions for tax, product, regulatory, and site advisers should stay in their own briefs. Ask each adviser to identify the facts reviewed, the question answered, the limits of the answer, and the owner of any follow-up. For background before those briefs, review this manufacturer-focused guide to India labour-law scoping. It is context for further review, not proof that an EOR covers another workstream.

What to request from an EOR provider

• The name of the contracting entity and the registrations the provider claims are relevant to the proposed employment administration.
• The proposed employment document, payroll output, invoice, and written division of employment-administration tasks.
• A written breakdown separating compensation, stated contributions and benefits, and the provider's service charge, without assuming that one quoted fee includes every item.
• Written exclusions for product, tax, establishment, regulatory, and site obligations.
• The provider's explanation of how the proposed scope changes if the person's role, authority, or work location changes.

Treat provider materials as descriptions of the provider's proposed service, not as proof of law or an entity-specific compliance conclusion. Verify legal and employment conclusions against the facts.

What evidence should the decision record contain?

Use one evidence log for the proposed arrangement. Give every item a clear label. A link alone is not enough because a page or draft can change. The log is a management record, not proof that a legal duty has been met.

Record these fields for each item:

• Workstream and the exact question the item is meant to answer.
• Document title, version, date received, and source.
• Provider entity or adviser that supplied it.
• Worker, role, location, or planned activity to which it relates.
• Contract clause or proposal section, when the item describes service scope.
• Internal owner and the person responsible for review.
• Review status: received, checked, unresolved, replaced, or not applicable to the stated plan.
• Limits, assumptions, missing facts, and the next question.
• Decision date and the name of the person who approved the recorded conclusion.

Keep provider claims separate from adviser conclusions. Keep drafts separate from signed documents. If two records conflict, mark the question as unresolved. Do not select the more convenient answer without review. If a role, location, authority, activity, entity, or site changes, note which earlier evidence may no longer fit. This process creates a traceable file. It does not turn a commercial document into a legal conclusion.

Which boundaries should remain explicit?

The memo should repeat its limits in plain terms so readers do not fill gaps with assumptions:

• Employment administration is the only EOR service scope assessed in this guide.
• Product obligations remain a separate workstream.
• Tax and establishment questions remain a separate workstream.
• Regulatory permissions remain a separate workstream.
• Factory, warehouse, inventory, machinery, import, and other site questions remain a separate workstream.
• A provider statement describes its proposed service unless independent review supports a wider conclusion.
• A sample output shows format and process. It does not prove that the output will fit every worker or fact pattern.
• An unresolved field stays unresolved until the named owner records suitable evidence or advice.

These boundaries do not decide which obligations apply. They keep the team from treating one contract as an answer to every India question.

How should a manufacturer make the decision?

Start with the responsibility table, not a vendor ranking. Complete the employment-administration row from the proposed contract. Ask the owners of product, tax, establishment, regulatory, and site questions to complete their own rows. Mark missing evidence as unresolved.

An EOR proposal can then be assessed for the scope actually offered. This process does not establish that the arrangement complies with any particular legal requirement. Obtain fact-specific advice before signing or relying on a legal, tax, or employment conclusion.

FAQ

What is the meaning of Employer of Record in India?

For this decision memo, EOR means a proposed provider for employment administration while the manufacturer directs the person's work. This is a working commercial definition, not a statement that Indian law provides one universal EOR structure. Confirm the proposed arrangement against the facts.

What should an employer of record India salary quote show?

Ask the provider to separate employee compensation, stated contributions and benefits, and its service charge. Do not assume a bundled quote establishes the applicable amount or satisfies an employment obligation. Verify those points for the proposed worker and arrangement.

How should I assess employer of record India reviews?

Use reviews to form questions about the service described by customers, then test those questions against the proposed contract, sample outputs, and provider evidence. Do not use a review or commercial vendor page as proof of law, tax treatment, cost, or compliance.

Which is the best EOR in India?

This guide does not recommend or rank a provider. Compare the contracting entity, written employment-administration scope, stated exclusions, evidence supplied, and handling of changes to role, authority, or work location. Keep product, tax, establishment, regulatory, and site decisions in separate workstreams.

Do EOR services in India prevent permanent-establishment exposure?

No conclusion is made here. Obtain fact-specific tax advice and do not treat an EOR contract or vendor description as proof that exposure has been eliminated.

Can an EOR cover a manufacturer's factory or site obligations?

Do not infer site coverage from an employment-administration contract. Record factory, warehouse, inventory, machinery, import, product, regulatory, tax, and establishment questions as separate workstreams. Obtain the relevant fact-specific assessment.

Need a responsibility map for your proposed India setup? Talk to Tensor Advisory to separate the employment-administration scope from the product, tax, establishment, regulatory, and site questions before you choose a provider or entity path.

Written by Tileo, an operator with a decade of Europe-Asia industrial trade programs.