Expanding through an Employer of Record (EOR) in India gives you a fast, compliant path to start hiring without needing to set up a local entity.

But EOR onboarding in India still involves specific operational steps that still need to move on time to avoid delays or compliance risk.

This blog walks through what needs to happen from offer release through the first month on the job (employee fully active), and what parts are typically owned, coordinated, or left to your team.

Let’s begin.

For a detailed overview, see: What Is an Employer of Record (EOR)? India Guide for Founders

EOR onboarding steps in India

Once the candidate is finalized, here’s how it typically unfolds:

Offer release and initial setup triggers

Collecting identity and bank documents, issuing an India-compliant contract, and triggering the next onboarding steps, such as background checks and compliance setup.

Some platforms, like Oyster and Deel, require agreement signature and initial deposit before issuing contracts — which can delay this step by several days.

Notice period coordination

In India, notice periods typically range from 30 to 60 days. During this time, background checks must be run, hardware needs confirmed and, if supported, arranged for delivery, and the candidate kept engaged.

If hardware coordination or engagement is skipped here, Day 1 often begins with delays or uncertainty.

Day 1: Systems and statutory setup

Email and Slack access, HRMS login, PF (India’s mandatory retirement savings scheme) and tax form submissions, insurance onboarding, and a formal orientation on policies such as POSH (India’s anti-harassment compliance law. Required for legal compliance – failure to complete it puts the employer at risk during audits.)

In most EOR models, device procurement and employee orientation on policies and benefits are not included. These tasks fall back on the founder or internal team.

Day 1–30: Ongoing follow-through

Payroll must be processed, benefits activated, and local support available if issues arise. Founders should also have visibility into any unresolved compliance, hardware, or documentation items.

In most global EOR setups, support runs through ticket queues. Few offer proactive updates to founders or local support to resolve issues; these often require manual follow-up or escalation.

See also: Hiring in India through an EOR? Here’s what founders miss without local support

Offer release and initial setup through an EOR

Onboarding begins once a candidate is finalized and the offer is ready to issue. This step sets up everything that follows — from background checks to payroll — but timelines often depend on the EOR’s internal process and what it requires from you before releasing the contract.

Here’s what needs to happen at this stage:

Collect basic documents

Before the offer can be issued, the EOR needs to collect identity and payroll documents from the candidate, typically their tax ID (called PAN in India), proof of address, and bank account details. These are required for payroll registration and compliance filings.

Some platforms don’t collect these until after the contract is signed, which can delay payroll setup or background checks that depend on this data.

Issue a compliant offer letter

The EOR must generate an India-compliant contract that reflects the employee’s full compensation (CTC), notice period, PF eligibility (India’s mandatory retirement contribution), and any other required terms.

With some global EOR platforms, this step is gated. Deel and Oyster, for instance, require the founder to sign their own service agreement and make an upfront payment before the employment contract is issued. This can delay contract release by several days, depending on how quickly the agreement is signed and the deposit is made.

Remote also requires the candidate to upload personal documents before their team begins contract drafting.

Trigger the next EOR onboarding steps

Once the candidate signs the offer, the next steps — like background checks, welcome calls, and hardware coordination — should begin immediately.

On many platforms, these aren’t automatic. Background checks often require a separate ticket. If hardware is supported at all, it usually needs to be scoped, quoted, and tracked manually by the India head or the founder.

Finalize internal documentation

Some EORs also require a Scope of Work (SOW), a short summary of the role, compensation, and reporting line, to be signed and stored for audit or internal approvals.

Some EORs bundle this with the contract. Others request it separately, and if there’s no clear prompt, it can stall the setup without the founder realizing it.

What founders should see

At this point, you shouldn’t need to follow up. Once a candidate is confirmed, the offer should be issued quickly, and signing it should trigger everything else – document tracking, onboarding milestones, and early coordination with the employee.

TeemGenie issues a compliant offer letter within one business day of confirmation. Once signed, it’s logged internally and all onboarding steps are initiated. No manual follow-up or workflow tracking is needed on your side. The SOW and offer are finalized together, and shared for your records.

For common execution gaps after onboarding begins, see: Choosing an EOR in India? Don’t Miss These Execution Gaps

What should move during the notice period

Once the offer is signed, the focus shifts to coordination during the notice period, a phase that lasts anywhere from 30 to 60 days in most India-based roles.

Several things need to move forward in parallel here to avoid delays on Day 1:

Background verification

This is time-sensitive and often has dependencies on ID/address documents, education and employment proofs, and candidate responsiveness.

Many platforms (e.g. Deel, Remote, Skuad) offer background verification as an optional service or integrate with external vendors, but the process often runs in a silo unless someone is actively tracking it.

If documents are incomplete or stalled, delays are common, and many global EOR platforms don’t step in unless prompted.

Hardware coordination (if supported)

If your EOR handles devices, this is when specs should be finalized, vendor quotes approved, payment initiated, and delivery coordinated. Most global platforms don’t include hardware provisioning by default — Remote and Oyster explicitly say it’s the client’s responsibility. Multiplier recently added a device provisioning feature that includes shipping and tracking, but only for clients who scope it.

Candidate engagement

This is one of the most overlooked steps. Some platforms send an automated welcome email or onboarding checklist, but few engage directly during the waiting period.

Oyster is a partial exception — they offer to explain the EOR model to the candidate, with client approval). But for most providers, founders are on their own when it comes to answering questions, sharing team updates, or preventing cold feet.

What this looks like with TeemGenie:

TeemGenie initiates a welcome call with the candidate to walk them through onboarding, documents, timelines, and what to expect

• A follow-up email is sent with next steps and a named contact

• Background checks are run with real-time updates and intervention if issues arise

• Hardware is handled end-to-end, including specs, vendor coordination, and tracked delivery

• Founders receive ongoing updates — no follow-ups or guesswork required

From Day 1 to 30: Compliance, onboarding, benefits & support

Day 1 is the formal start of employment — but being legally employed doesn’t always mean the employee is work-ready. The difference comes down to what has been coordinated ahead of time, and whether follow-through continues beyond Day 1.

This stage includes three categories of onboarding:

1. Compliance and payroll activation

On Day 1, the EOR must complete India’s statutory employer actions:

• Provident Fund (PF) registration and Form 11 submission

• Professional Tax registration (state-specific)

• POSH policy acknowledgment and compliance tracking

• Scam-awareness documentation (e.g. impersonation risks)

Many platforms (like Deel and Remote) only begin filings after the employee uploads required forms, often post–Day 1. Delays here can affect payroll eligibility or benefit activation.

To ensure the first payroll run is accurate, the EOR also needs to:

• Confirm bank account details and salary components

• Link PF account with the employee’s UAN, if applicable

• Deduct the correct Professional Tax based on state

• Complete benefit enrollment (insurance, etc.)

If these aren’t coordinated during notice, the first payroll run may be delayed or show incorrect deductions.

2. Benefit access and orientation

Most global EORs include insurance and statutory benefits in the contract, but in practice:

Activation may be delayed until post–Day 1

Employees often receive no onboarding on how to use or access them

Some platforms require the employee to enroll manually via portal

For founders, that means uncertainty about when benefits go live or whether employees know how to use them. If your team promised a certain policy or tier of coverage, you’ll need to check it’s been implemented correctly.

3. Tools and support access

While work-specific systems (e.g., GitHub, internal tools) are your responsibility, EORs are expected to:

• Set up access to their HR portal (for payslips, reimbursements, etc.)

• Enable communication with HR support

• Securely provision any shared accounts they provide (e.g., email)

Few platforms configure access with proper security layers unless requested. Most rely on generic portals and ticketing queues, and offer limited visibility into what’s still pending or what the employee may be waiting on.

With TeemGenie, this looks like:

• All statutory filings pre-filled and triggered automatically on Day 1

• Insurance activated Day 1, with policy documents and walkthrough shared

• TeemGenie-hosted email set up with two-factor authentication (2FA) for secure access

• HRMS login shared for payslips, reimbursements, and leave tracking

• Slack channel access with a local HR contact for questions and support

• POSH and scam-awareness materials delivered and tracked

• No delays or dependencies on manual employee uploads

Unlike platforms that start these workflows after Day 1 — or leave them to be tracked manually — TeemGenie completes setup during the notice period and verifies follow-through before payroll is processed. Founders receive updates throughout; there’s no need to escalate or chase open items.

How EOR onboarding differs across providers

Not all EORs own the same parts of onboarding. Some trigger actions only after employee inputs. Others defer coordination entirely. Here’s how top global EOR platforms compare across each key step, and what a full-scope partner like TeemGenie handles differently.

S

Conclusion

Choosing the right EOR partner comes down to how much on-the-ground support your team will need, and whether that’s included, coordinated, or left to you.

If your team already has someone in India — HR, admin, or a country lead — you may be able to coordinate some of these steps internally. But if you’re relying on an EOR as the only layer between offer release and a work-ready hire, that layer needs to include more than just contracts and payroll.

That’s where most founders hit friction: hardware delays, missed follow-ups, unclear support paths, or having to manually check what’s been completed.

TeemGenie was built to close those gaps, with full ownership of every onboarding step, locally coordinated support, and proactive updates throughout.

If you’re comparing EORs or trying to assess how much support your team will need on the ground, we’re happy to walk you through what to look for, and how TeemGenie handles it.

👉 Book a 15-minute call with our India expansion experts.