.png)
What Are the EOR Payroll Compliance Rules for India and Canada?
- Saransh Garg
- 2 days ago
- 9 min read
Under India's Code on Wages, basic pay can no longer be structured below 50% of total compensation, and that single rule quietly rewrote every payroll calculation for Indian tech talent working on Canadian budgets. Add Canada's provincial Employment Standards Acts, the Canada Labour Code, and CPP and EI remittance rules on top, and you get two overlapping compliance systems that most HR teams only discover after something has already gone wrong. We've run EOR payroll compliance rules for India and Canada across dozens of mandates, and the mistakes are almost always the same: treating this as a single country problem when it is really two.
Why Canadian Companies Are Hiring Indian Tech Talent Through EOR
Canadian tech hiring hasn't slowed, it has just shifted offshore. Toronto's fintech companies, Vancouver's gaming and AI studios, and Ottawa's enterprise software firms are quietly running distributed engineering teams that sit partly in India. Canadian intermediate developer salaries have climbed past CAD 95,000 to 115,000 a year, and the domestic supply of senior DevOps and cloud cost optimization talent hasn't kept pace with demand in Toronto and Vancouver.
What we see repeatedly: Canadian companies that hire remote Indian contractors directly through a simple consulting agreement, then get flagged during a payroll audit because the "contractor" works exclusively for one client on fixed hours using company equipment. That is misclassification, and it is exactly what pushes companies toward proper EOR payroll compliance rules for India and Canada instead of a contractor workaround.
AI adoption has changed what Canadian companies want from an Indian hire too. It is no longer just backend developers. Clients now ask for engineers comfortable working alongside AI coding assistants, managing agentic workflows, and optimizing cloud spend as teams scale AI infrastructure. That shift has made contract hiring more attractive than a slow entity setup, since teams need to flex up and down as pilots mature into production workloads. Setting up an Indian entity still takes 8 to 12 weeks, versus a 2 to 3 week EOR onboarding.
Which Indian Cities Have the Best Talent for Canadian EOR Hiring?
Sourcing depends on the role. Bengaluru has the deepest bench for cloud native and Kubernetes heavy DevOps work, since most candidates there already operate across AWS and GCP simultaneously. Pune and Hyderabad produce strong enterprise developers who suit Canadian insurance and banking clients running legacy stacks alongside newer microservices. Chennai has become a reliable source for QA automation and backend engineers used to regulated environments, which fits Canadian healthtech and fintech clients working under PIPEDA data rules.
This is also where the contract versus full time hiring decision matters most. Most Canadian clients start with a contract hire through an EOR: lower commitment, faster onboarding, easy to scale a pilot team up or down. Once a role proves out over 12 to 18 months, many convert that engineer to full time, either through the EOR converting the employment or through the client opening its own Indian entity. AnjuSmriti Global builds both paths into the same original contract, so a client never has to renegotiate from scratch to convert someone from contract to permanent.
What Indian engineers bring to Canadian mandates: strong hands on cloud certification density, since AWS and Azure certifications are more common among Indian mid level candidates than their Canadian counterparts at the same seniority.
What they typically lack, and what we test for directly: comfort with async first documentation habits, and working across a genuine 10 to 13 hour time gap without a dedicated overlap shift. Our vetting for Canada bound roles includes a live pairing session with a Canada based technical lead, not just a take home assignment.
EOR Payroll Compliance Rules for India and Canada, Explained
Here is the part most companies get wrong: they assume only one country's law applies, when EOR payroll compliance rules for India and Canada actually apply simultaneously, to different parts of the arrangement.
On the India side, the Indian EOR is the legal employer under Indian law. Payroll must comply with the Code on Wages (basic pay at minimum 50% of total compensation), the Code on Social Security (provident fund, ESI, and gratuity, now accruing pro rata after just one year of continuous service for fixed term employees), and the applicable state Shops and Establishments Act governing hours and leave. Gratuity catches Canadian companies off guard most often: many EOR contracts run 12 to 36 months, which used to mean no gratuity liability at all under the old five year rule. That has changed.
On the Canada side, the company carries risk even though it is not the direct employer. The main exposure is permanent establishment risk under Canadian tax law: if the Indian engineer is seen as exercising authority on the Canadian company's behalf, such as signing contracts or approving spend, tax authorities can argue the company has a taxable presence it never intended to create. The second exposure is misclassification, which falls under the relevant provincial Employment Standards Act or the federal Canada Labour Code for regulated industries like banking.
The clause we check most carefully is IP assignment. An engineer employed by an Indian EOR, building software owned by a Canadian company, needs an assignment clause valid under both India's Copyright Act work for hire provisions and Canadian ownership expectations. A generic template pulled from a US agreement often does not hold up if the EOR itself is not named as assignor.
India-Canada EOR Payroll Compliance Checklist
This is the checklist we hand every new HR contact on a Canada bound mandate, distilled from the EOR payroll compliance rules for India and Canada covered above.
Compliance Area | India Side Requirement | Canada Side Requirement | Who Owns It |
Wage structure | Basic pay at least 50% of total pay | No direct obligation, client pays gross invoice | Indian EOR |
Statutory deductions | Provident fund and ESI where applicable | None unless employee becomes Canada resident | Indian EOR |
Leave entitlement | State Shops and Establishments Act minimums | Not applicable | Indian EOR |
Gratuity | Accrues pro rata from year one for fixed term roles | Not applicable | Indian EOR |
Termination notice | Per Industrial Relations Code and state rules | Contract notice clause should mirror this | Both parties |
IP assignment | Must name EOR, client, and employee jointly | Must match Canadian ownership expectations | Client and EOR |
Permanent establishment | Engineer should not sign contracts for client | Tax counsel should review authority limits | Client |
Data handling | India IT Act data rules | PIPEDA compliance for Canadian customer data | Client with EOR support |
The line item companies miss most is permanent establishment risk. Teams obsess over payroll math and forget that one badly worded clause giving an engineer spending or signing authority can trigger a tax inquiry that costs more than any payroll saving.
How We Run India-to-Canada EOR Placements, Step by Step
Our standard timeline runs 15 to 20 business days from signed mandate to first payroll: about a week for shortlisting and vetting, 3 to 4 days for contract execution, and 5 to 7 days for onboarding and payroll setup. That is slower than hiring locally, but far faster than the 8 to 12 weeks an Indian entity setup requires.
A recent example: a mid size Toronto healthtech company needed three backend engineers for a PIPEDA sensitive patient data platform, on a 12 month contract with an option to convert to full time hiring in year two. Their original engagement letter gave the lead engineer authority to approve infrastructure spend up to $10,000, language that inadvertently created the kind of decision making authority that raises permanent establishment questions.
We flagged it during contract review, the client's own tax counsel rewrote the clause, and all three engineers were live on payroll within 18 days. Eighteen months later, two of the three converted from contract to full time hiring once the client opened its own Bengaluru entity. The EOR had done its job as a bridge, not a permanent structure.
How Much Does EOR Hiring Between India and Canada Actually Cost?
Real numbers, based on current placements for Canadian clients hiring backend and DevOps engineers through an Indian EOR:
Mid level (3 to 5 years): India contract rate roughly CAD 1,450 to 2,250 a month, versus a Canadian direct hire at CAD 6,500 to 7,500 a month gross.
Senior (6 to 9 years): India contract rate roughly CAD 2,550 to 3,700 a month, versus a Canadian direct hire at CAD 8,300 to 9,600 a month gross.
Lead or architect (10 plus years): India contract rate roughly CAD 3,850 to 5,450 a month, versus a Canadian direct hire at CAD 10,500 to 13,000 a month gross.
On top of the contract rate, budget for employer provident fund contribution, gratuity accrual, the Indian EOR's management fee, and our recruitment fee. All in, most clients land at 45 to 55 percent of the equivalent Canadian direct hire cost, once every line item under the EOR payroll compliance rules for India and Canada is accounted for.
This is also where the contract versus full time math changes. Contract hiring through EOR keeps costs variable and avoids long term severance exposure, which suits pilot teams and AI proof of concept work. Full time hiring, once a role proves out, usually lowers the monthly management fee and gives more control over benefits, but adds the notice and gratuity obligations built into Indian labour law. Most clients run a mixed model: a few full time core engineers with a flexible contract layer around them.
Conclusion
Expect India's labour codes to keep evolving as state level rules get finalized, and companies that set up their EOR arrangement early will likely need a compliance refresh rather than a simple renewal. What we're seeing right now, in live mandates, is Canadian HR teams asking about permanent establishment risk unprompted, a question almost nobody asked a couple of years ago. Getting EOR payroll compliance rules for India and Canada right from day one is the difference between a placement that scales smoothly and one that becomes an audit headache down the line.
If you're planning a Canada to India EOR hire, talk to our team here.
Interesting Reads:
FAQs
1.Does Canadian employment law apply to an Indian engineer hired through an EOR?
No. If the engineer is based in India and employed by the Indian EOR, Canadian employment standards do not apply to that relationship at all. Canadian law still governs the commercial agreement between your company and the EOR, so it is worth having your own counsel review that agreement separately from the Indian employment contract itself, especially the clauses on liability and scope.
2.How does India's Code on Wages affect salary structure for EOR hires?
Basic pay must equal at least 50% of total compensation, which changes provident fund and gratuity calculations since both are based on basic pay. This usually means a modest increase in statutory contributions rather than a change in gross cost, but it should be budgeted for in new contracts and reviewed carefully at renewal.
3.Who handles CPP and EI for an India based EOR employee?
Nobody withholds CPP or EI in this arrangement, since these are Canadian programs tied specifically to work performed inside Canada. An India based engineer contributes to India's provident fund and ESI system instead, through the Indian EOR's monthly payroll run. This only changes if the engineer later relocates to Canada or becomes a Canadian tax resident while still working for the same client.
4.Can a Canadian company create a permanent establishment in India through an EOR?
It is a real but manageable risk. It typically arises when an India based employee is seen as habitually signing contracts or approving spend on the company's behalf, not from the EOR relationship itself. Keeping contract signing and spend approval authority with Canada based staff, and writing that limit explicitly into the engagement letter, largely removes the exposure for most engineering focused mandates.
5.What happens to gratuity if a Canadian company ends an EOR contract early?
Gratuity now accrues pro rata from one year of continuous service for fixed term roles. Ending a contract after 14 or 18 months can trigger a gratuity payout that would not have existed under the older five year rule, so it should be priced into the budget and written clearly into the termination clause upfront.
6.How is IP ownership handled across an Indian EOR and a Canadian client?
The assignment clause should name the EOR, the client, and the employee together, since Indian copyright law's work for hire rules can create ambiguity about who the employer actually is inside an EOR structure. A generic clause copied from a US or European template often misses this three way naming, which is exactly where disputes tend to surface later.
7.Is contract hiring or full time hiring better for a Canada India EOR arrangement?
Contract hiring suits pilots, AI proof of concept work, and roles still being defined, since it keeps cost variable and avoids long notice obligations. Full time hiring suits proven roles where the client wants more control over benefits design and a lower ongoing management fee. Most Canadian clients start with contract hiring and convert specific roles to full time later.
8.How long does onboarding take for an Indian EOR hire working with a Canadian company?
Typically 15 to 20 business days from signed mandate to first payroll, covering vetting, contract execution, and onboarding. That is slower than a local hire but much faster than the 8 to 12 weeks needed to open an Indian entity from scratch.
Comments