top of page

What SLAs Should You Expect From an India EOR Provider?

Writer: Saransh Garg
Saransh Garg
Aug 5
9 min read

Updated: Aug 10

India EOR provider SLA

A properly run India EOR should confirm a candidate's compliant onboarding, including PF registration, ESI enrollment, and a Shops and Establishment compliant contract, within 3 to 5 working days of offer acceptance. If your current provider is quoting two to three weeks for this, or cannot tell you their payroll run SLA in writing, that is the first sign your contract has no enforceable service standards at all. When HR teams ask us what SLAs should you expect from an India EOR provider, we always start here. An EOR without written, penalty backed SLAs is not really an EOR, it is a payroll vendor wearing an EOR's marketing.


We have audited dozens of EOR contracts for clients who came to us after a bad experience elsewhere, and the pattern is consistent. Vague language like "prompt onboarding" or "timely payroll," with no numbers attached.


Why HR Teams Keep Getting Burned on India EOR Timelines

India's EOR market has grown fast, and a lot of that growth has come from generalist global payroll platforms bolting on an "India entity" service without local compliance depth. We see the fallout regularly. A Delhi NCR based fintech client came to us after their previous EOR missed two consecutive PF (Provident Fund) remittance deadlines. Under the EPF Act, this attracts damages under Section 14B that can run up to 25% of the defaulted amount, charged to the employer of record, not the client. Still, the client had to explain the delay to their own board.


The structural problem is that India does not have one labour code. It has a layered system of central acts (the EPF Act, the ESI Act, the Payment of Wages Act, 1936) sitting on top of state specific Shops and Establishment Acts that vary by where the employee is physically based. A DevOps engineer on payroll in Bengaluru is governed by the Karnataka Shops and Commercial Establishments Act. The same role in Pune falls under the Maharashtra Act, with different working hours registers and leave encashment rules. An EOR provider running a single national process for every city is, structurally, unable to guarantee compliance SLAs.


Workforce planning has also gotten more automated. AI powered compliance dashboards and automated statutory filing tools are now common across serious EOR platforms, flagging PF or ESI mismatches before a filing deadline instead of after. At AnjuSmriti Global, we treat these tools as a support layer, not a replacement for a compliance team that actually understands state level law. Software catches patterns. It does not know that a Chennai based hire needs a different registration template than a Bengaluru one.


What Onboarding SLA Should an India EOR Provider Commit To?

Most EOR sales decks say "fast onboarding." Almost none define what is inside that window. When we set up a new employee for a client, our onboarding SLA covers four discrete, individually timed steps, and we tell clients which one we are on at each stage.

  1. Offer to contract issuance, 24 to 48 hours after the client confirms terms.

  2. Statutory registration, PF (EPFO), ESI if gross salary is under ₹21,000 per month, and Professional Tax registration, completed within 3 working days of the signed contract.

  3. Payroll system setup, bank account verification, Form 16 setup, and first payroll cycle mapping, completed before the employee's start date, never after.

  4. Day one readiness confirmation, a written confirmation to the client that the employee is compliant and payroll ready, not a verbal assurance.

This is the kind of detail Indian engineers assume is already handled, and one that non Indian HR teams often do not think to ask about until the first payroll cycle throws an error because ESI was not checked near the threshold.


A reliable Employer of Record (EOR) in India should commit to clear service-level agreements: employee onboarding within 3–5 business days, payroll accuracy above 99.5%, and compliance query responses within 24–48 hours. Ask any provider to put these commitments in writing before you sign.

We test for this in every mandate rather than assuming a role is obviously above the ESI cutoff. It is exactly this level of detail that answers the SLAs should you expect from an India EOR provider question better than any generic sales pitch.


Contract Hiring vs Full-Time Hiring: How the SLAs Actually Differ

A lot of confusion around India EOR SLAs comes from treating contract hiring and full-time hiring as the same product. They are not, and the SLA timelines reflect that.


Contract hiring places a professional on a defined statement of work, usually tied to a project scope and duration. Statutory registration is lighter (ESI applicability still depends on gross pay, but Professional Tax and gratuity provisions often do not apply the same way), so onboarding can reasonably run 3 to 4 working days.


Full-time hiring through an EOR brings the complete benefits structure into play: gratuity provisioning, leave encashment policy, and a longer term employment contract under the applicable state Shops and Establishment Act. Onboarding for full-time roles typically runs 5 to 7 working days because there is more to register and more to explain to the employee at day one. If a provider quotes one blended onboarding number for both hiring types, ask them to split it. The faster figure is usually the one being advertised, while the slower one applies to whichever hire you actually need.


The SLAs Should You Expect From an India EOR Provider: A Checklist

Here is the framework we hand every prospective client during due diligence. If an EOR cannot put numbers against each row in writing, that is your answer about how seriously they take compliance.

SLA Category

Standard You Should Get in Writing

Statutory Reference

Contract issuance

24 to 48 hours after offer confirmation

Indian Contract Act, 1872

Statutory registration (PF, ESI, PT)

Within 3 working days of signed contract

EPF Act, 1952; ESI Act, 1948

First payroll readiness

Complete before employee start date

Payment of Wages Act, 1936

Monthly payroll disbursement

By the 1st to 7th working day of the month

Payment of Wages Act, 1936

PF remittance

By the 15th of the following month

EPF and MP Act, 1952

ESI remittance

By the 21st of the following month

ESI Act, 1948

Compliance escalation response

Under 4 business hours for urgent flags

Internal SLA

Offboarding and full and final settlement

Within 45 days of last working day

Payment of Wages Act, 1936

The escalation response row is the one clients underrate most until they need it. A payroll error that is not flagged and fixed within hours, not days, becomes a trust problem with your India based employee, and retention in a competitive market depends on that person never feeling like a second class hire compared to headquarters staff.


How We Deliver on These SLAs, and What Almost Went Wrong Once

Our onboarding to first payroll SLA is 5 working days for standard roles and 7 for roles requiring specialised registration under certain state acts. We assess EOR readiness the same way we assess a candidate, with a checklist, not a gut feeling. Contract drafted against the correct state act, PF and ESI applicability confirmed against actual gross pay, and a named compliance point of contact assigned before day one.


A mid sized European SaaS company, roughly 200 employees globally, engaged us to move 14 India based contractors onto an EOR structure after their existing arrangement was flagged during a funding round's legal due diligence. Two of the contractors were based in Chennai, governed by the Tamil Nadu Shops and Establishments Act, which our first pass registration template had not accounted for correctly since it was built around the Delhi and Karnataka variants we handle most often.


We caught the mismatch during our internal pre go live audit, not after a filing deadline was missed, and corrected the registration within 48 hours, inside our own escalation SLA. The transition completed in 9 working days across all 14 contractors, with zero missed payroll cycles and zero compliance flags in the funding round's follow up audit.


What Does an India EOR Provider Cost, and What Should You Reinvest the Savings Into?

EOR pricing in India typically runs 8% to 15% of gross monthly salary as the management fee, on top of statutory employer contributions of roughly 13% to 14% (PF employer contribution at 12% of basic pay, plus administrative charges, plus gratuity provisioning). For a mid level engineer on a ₹18,00,000 annual gross salary, total employer cost including the EOR fee typically lands between ₹21,50,000 and ₹22,80,000 annually, depending on the provider's fee tier and whether gratuity is provisioned monthly or accrued.


Providers quoting fees at the low end of that range (6% to 8%) are worth scrutinising closely. The SLAs should you expect from an India EOR provider at that price point rarely hold up in practice, since the compliance commitments above require dedicated staff per state, and that staffing cost has to come from somewhere. Clients who move from a cut rate provider to a properly staffed one tend to reinvest the fee difference into faster hiring cycles elsewhere, since the time HR previously spent chasing payroll errors gets freed up for actual IT hiring and team building instead.


Conclusion

India's new labour codes, consolidating the Payment of Wages Act, the EPF Act, and others under the Code on Wages framework, are rolling out state by state and are set to tighten the compliance bar further rather than loosen it. This will separate EOR providers with real state level infrastructure from those running a single national template. Global capability centers continue to expand into tier two Indian cities, and cloud based compliance dashboards are becoming a baseline expectation rather than a nice to have.


In live mandates right now, we are seeing more finance and legal teams asking for SLA penalty clauses upfront during vendor selection, rather than discovering the gap after a missed filing. That tells us the market is finally catching up to how much SLA specificity actually matters. If you are evaluating providers, the real question to ask is not whether they offer SLAs. It is what SLAs should you expect from an India EOR provider in writing, with numbers, before you sign anything.

Ready to see our SLA terms in writing? Get in touch with our team.

Interesting Reads:


FAQs

1.Does an India EOR provider guarantee PF and ESI compliance?

Yes, since the EOR is the legal employer of record and carries direct statutory liability under the EPF Act and ESI Act. If a filing is missed, damages under Section 14B are assessed against the EOR, not your company. Ask for written remittance dates, the 15th for PF and the 21st for ESI, with a penalty clause attached, not just a general compliance statement.


2.What happens if our India EOR misses a payroll deadline?

Under the Payment of Wages Act, 1936, the EOR as legal employer is liable for delayed wages, and the employee can claim compensation directly from the EOR through the labour authority. Your company usually is not named in that claim, but reputational damage still lands on you, especially with senior engineers. Ask for a breach notification clause so you learn about it in hours, not after the employee escalates.


3.How does the Shops and Establishment Act affect EOR SLA timelines?

It is state legislation, so an employee's contract and leave rules follow the act of the state where they are based. Karnataka's version differs from Tamil Nadu's or Maharashtra's in registration steps and renewal cycles. A provider running one national template without state specific variants will either under comply somewhere or promise timelines it cannot consistently meet across every city.


4.Should our India EOR contract cover offboarding, not just onboarding?

Yes, and this is the most commonly missed clause we see. Full and final settlement, including gratuity and leave encashment, should complete within 45 days of the last working day under standard practice, stated explicitly with a penalty for delay. Skipping this clause often means offboarding drags to 60 or 90 days, creating friction right when a clean exit matters most.


5.What escalation response time is reasonable for an India EOR provider?

For urgent payroll or compliance flags, a 4 business hour response is achievable for a provider with dedicated compliance staff. Anything beyond 24 hours suggests understaffing relative to client volume. For routine queries like payslips or leave balance, 24 hour resolution is standard. Ask for a provider's actual ticket resolution data from the past quarter, not just the number written into the contract.


6.Do SLA timelines differ for contract hires versus full-time EOR hires?

Yes. Contract hires under a statement of work usually need lighter statutory registration, so onboarding can run 3 to 4 days. Full-time hires bring gratuity, leave encashment, and a fuller benefits structure into scope, which typically pushes onboarding to 5 to 7 days. If a provider quotes one blended number, ask them to split it by hire type before you sign.


7.Can an India EOR provider realistically offer same-day onboarding?

Same day statutory registration is not realistic under Indian compliance requirements, since PF and ESI registration involve document verification that takes a minimum of 24 to 48 hours even with an efficient team. A same day claim usually means the employee starts working before compliance is actually complete, which is a real liability gap. Offer letter issuance can reasonably be same day. Statutory compliance cannot.


8.What SLA penalty structure is fair if an India EOR provider misses a commitment?

A service credit model works well in practice, where a percentage of that month's management fee is waived per missed SLA and scales with severity. Avoid contracts with no penalty structure at all, or ones that cap liability so low it creates no real incentive. If the maximum penalty is less than one month's fee, it is not functioning as a deterrent.

 
 
 

Comments


bottom of page