PEO Agreement in India: What to Check Before You Sign

You have shortlisted a provider, the pricing looks reasonable, and now a 20-page contract is sitting in your inbox waiting for a signature. The parts that decide who carries risk, what you actually pay each month, and how you exit are usually the parts buyers skim.

We sit on the provider side of these agreements in India every week. This guide covers the clauses founders, CFOs, and legal leads tell us they wish they had read line by line before signing, separate from the question of which provider to shortlist in the first place.

What is a PEO agreement in India, and what does it cover?

A PEO agreement is the contract that governs how a provider runs payroll, benefits, and statutory compliance while you direct daily work. The clause that matters most names the legal employer.

Here is what the agreement actually covers:

• Employment relationship: which single entity is the legal employer of each worker.
• Fee structure: the management fee, statutory contributions, and pass-through costs.
• Data handling: your role as data fiduciary and the provider's as data processor.
• IP ownership: written assignment of work product for employees and contractors.
• Liability and exit: who carries statutory risk and how you leave the arrangement.

For how the model works end to end, from cost to compliance, read our PEO in India guide.

Most templates gloss over one wrinkle. The classic PEO "co-employment" model, where a client and a provider share employer status, does not map onto Indian law. India recognizes one legal employer per worker, and co-employment is not a statutory category. In practice, that means a service marketed as a "PEO" in India works one of two ways:

• You hold an Indian entity: you remain the legal employer, and the provider administers payroll and compliance for you.
• You have no entity: the arrangement is really an Employer of Record, where the provider is the legal employer.

For the full breakdown, read our note on co-employment versus joint employment in India and our guide to EOR versus PEO in India.

Which clauses decide where liability sits?

Liability sits wherever the agreement places the legal employer. India recognizes one legal employer per worker, so the contract has to name a single entity, with commercial recourse to the provider through the indemnity clause.

The two clauses that decide your real exposure:

• Legal-employer clause: statutory liability for a late or wrong filing attaches here first. If you hold an Indian entity and run the PEO model, a missed PF deposit or an incorrect TDS filing is your liability, and your only path to recovery is contractual.
• Indemnity clause: your contractual route to recover losses from the provider. Read it for three things: whether it runs in your favor for provider errors, whether it carries a cap, and what that cap actually is.

A cap expressed as a clear rupee figure is far stronger than one pegged to "fees paid," which can be a fraction of the real exposure on a payroll error. If the model is EOR instead, the provider is the legal employer and carries the primary statutory liability, which shifts the balance in your favor.

What should the fee and pass-through schedule spell out?

The fee schedule should separate the provider's management fee from statutory contributions and pass-through costs. Ambiguity here is where margin quietly hides.

What the fee schedule should itemize:

• Management fee: the provider's own charge, with 18% GST applied on top of it.
• Statutory contributions: PF, ESI, and similar, stated as billed at cost or with a named margin.
• Pass-through costs: benefits, insurance, and one-off items shown separately from the fee.
• FX terms: the rate source, the timing of the conversion, and any buffer.

Two questions settle most of this.

First, ask directly whether employer PF, ESI, and other statutory contributions are billed at cost or with a percentage added on top. Both are legitimate, but you want to know which one you are agreeing to before the first invoice.

Second, pin down currency: a provider converting your USD to rupees sets a rate somewhere, and the source, the timing, and any buffer all move the number you pay. Get those three points in writing.

For a fuller cost model, read our guide to the cost of a PEO in India, the pricing page, and the employee cost calculator.

What termination and exit terms should you insist on?

Insist on symmetric notice, a defined employee transfer path, and clarity on who bears severance. Exit is the clause buyers regret ignoring most, because you negotiate it when the relationship is good and need it when it is not.

What to lock down before signing:

• Symmetric notice: the same notice period on both sides, not a short window for the provider and a long one for you.
• Employee transfer path: a written process to move employees to another provider or to your own entity without losing accrued tenure or benefits.
• Fixed termination grounds: grounds set at signing, not left open to the provider's later discretion.
• Settlement responsibility: who funds gratuity, notice pay, and final dues on exit. If the agreement is silent, assume it lands on the legal employer.

Expert insight: ask for the exit clause to name a transition assistance period, say 30 to 60 days, during which the provider keeps running payroll while you stand up the next arrangement. That single addition prevents a gap where your team goes unpaid.

For the severance math behind final settlement, read our guide to the gratuity calculator.

What data-protection terms does the DPDP Act require?

The DPDP Act 2023 requires a written contract with your provider acting as a data processor, while you remain the data fiduciary. You stay accountable to your employees for how their personal data is handled, even when the provider does the day-to-day processing.

What that written contract must address:

• Purpose limits: the defined reasons the provider may process employee data.
• Security safeguards: the protections the provider applies to that data.
• Breach notification: a clear timeline for telling you when something goes wrong.
• Data deletion on exit: return or deletion of employee data at the end of the relationship.

In the language of the Act, you are the fiduciary who decides why and how employee data is processed, and the provider is the processor acting on your instructions.

The written contract between you is not optional; it is the instrument the law expects to see. Deletion on exit and a clear breach-notification timeline are the two points generic templates most often leave out.

Who owns IP and work product under the agreement?

IP assignment should be explicit for both employees and contractors. Under the Copyright Act 1957, the ownership defaults differ by relationship, so nothing should be left to assumption.

How the defaults split:

• Employee work (Section 17(c)): work created by an employee in the course of employment is owned by the employer by default, absent any agreement to the contrary.
• Commissioned contractor work: work commissioned from an independent contractor generally stays with the contractor, unless it falls within the narrow Section 17(b) list (photographs, portraits, engravings, and cinematograph films made for consideration).
• Why it matters: the ownership defaults differ by relationship, which is exactly why IP should be assigned explicitly in writing rather than relied on.

The risk is subtle. When a developer or designer sits with an EOR or PEO as the legal employer, the default ownership of what they create does not automatically flow to you, the client, unless the contracts say so explicitly.

This gets sharper with independent specialists, where commissioned-work rules differ from employee rules. Ask to see the IP-assignment language in both the master agreement and the individual employment or contractor contract, so you have an unbroken written chain from the worker, to the legal employer, to your company.

For compliant engagement of specialists with explicit IP terms, read about our Contractor of Record.

What are the red flags in a PEO agreement?

The clearest red flags all point to undefined risk or hidden cost. Any one of them deserves a hard question before you sign.

• No named legal employer: if the contract does not state which single entity employs each worker, the liability picture is undefined.
• Open-ended indemnity: an uncapped indemnity running against you, or a cap tied only to fees paid, leaves you exposed on a payroll error.
• Bundled fees: one lump sum with no split between management fee, contributions, and GST hides margin and makes audits hard.
• Unilateral termination terms: grounds the provider can revise after signing give you no stable footing on exit.
• Missing data terms: no written processor contract means a DPDP Act 2023 gap sitting on your side as fiduciary.
• Silent IP: no explicit assignment clause means work-product ownership is left to default rules you did not choose.

For help weighing one provider against another, read our guide to choosing the best PEO in India.

What should you ask before signing?

Before you sign, confirm six things in writing, and get each answer inside the contract, not in a reassuring email. The table below is the checklist we run with clients reviewing a draft.

Expert insight: send these six questions as a single written list and ask the provider to answer by citing the clause number in their own draft. A provider that answers fast and by reference is one you can work with; vague answers tell you where the next problem will be.

For a cost model to bring to the same review, use our employee cost calculator.

How does Wisemonk handle the employment contract in India?

Wisemonk is an India-native employer of record that helps global companies hire, pay, and manage employees without setting up a local entity. We have worked with 300+ clients and 2,000+ employees, process $20M+ in annual payroll, and hold a 4.8/5 rating on G2.

Here is how we make the employment contract side simple in India:

• EOR Services in India: we act as the legal employer so one named entity carries statutory liability, from $99 per employee per month.
• PEO services in India: for clients with their own Indian entity who need compliant payroll and administration, from $49 per employee per month.
• Contractor of Record: compliant engagement of independent specialists with explicit IP and assignment terms.
• Managed payroll: accurate payroll, statutory filings, and clear pass-through reporting on a custom quote.
• Background verification: pre-hire checks built into onboarding so your contracts rest on verified people.

Hear from industry leaders

Wisemonk is a key partner for EOM-Energy O&M Services, playing an essential role in supporting our operations. Their seamless payment solutions make transactions not only simple and fast but also reliable. The team's responsiveness, professionalism, and proactive approach give us complete confidence in every interaction. We look forward to strengthening our collaboration, using Wisemonk both for Employer of Record services and for recruitment support, to help us expand our team in India in the short and medium term.
- José Enrique Montero Pérez, CEO at EOM-Energy O&M Services, USA