Gig and platform workers in India come with compliance duties every contractor hiring company should know

Gig and platform workers in India got a formal seat in employment law for the first time under the Code on Social Security, 2020. By 2026, the paperwork obligations tied to that status stopped being theoretical. If you run a ride-hailing, delivery, logistics, e-marketplace, or freelance-platform business with India-facing operations, you now need to register every worker on the government’s eShram portal. You also have to report exits and file monthly updates, all in close to real time. If you don’t run a platform but you do hire India-based contractors directly, the same law still matters to you, just for a different reason.

The registration duty is live right now. The actual social security contribution aggregators will owe hasn’t switched on yet. That’s because the government still hasn’t notified the contribution rate. That gap won’t last. And the wider signal matters: India is building the machinery to see who’s really working for whom. That is exactly the kind of shift that turns a loosely worded contractor agreement into a misclassification claim.

What Gig and Platform Workers in India Actually Means Under the Law

India’s Code on Social Security, 2020 gave gig workers and platform workers their own legal definitions for the first time. These sit separate from “employee” and “independent contractor.” The code, along with the three other labour codes, came into force nationally on 21 November 2025, according to the EY alert on the notification. A gig worker, under the code, is someone earning from work arrangements outside a traditional employer-employee relationship. A platform worker is a gig worker a digital platform specifically engages. An aggregator is the platform business connecting them to end users.

The obligations on aggregators sit in the code’s Seventh Schedule. They’re specific rather than aspirational: real-time worker registration, exit reporting, and an eventual funding contribution. None of this touches how you treat a single freelancer you hired directly. It targets platform businesses instead.

The Nine Aggregator Categories the Law Actually Covers

The Seventh Schedule names nine categories of aggregator, based on the analysis from Taxmann’s review of the aggregator obligations. These cover ride sharing, food and grocery delivery, logistics, e-marketplaces for goods and services, professional services platforms, healthcare platforms, travel and hospitality, and content and media. A ninth category acts as a catch-all for any other platform connecting buyers and sellers. That catch-all is doing a lot of work. It is why freelance marketplaces and B2B service platforms should get a legal read on where they land.

Who Counts as an Aggregator, and Who Doesn’t

A single foreign company that hires one India-based contractor directly is not an aggregator. There’s no marketplace, no matching of multiple buyers to multiple sellers, just a bilateral contract. The law isn’t reaching into that relationship, at least not through the gig worker provisions.

But the boundary gets blurry fast. A freelance marketplace that lists India-based talent for clients to book could plausibly qualify as an aggregator under that ninth, catch-all category. So could an internal gig marketplace a GCC builds to route project work to contractors. If your model connects more than one buyer to more than one worker through a platform or app, don’t assume you’re outside the scope. Get a read from local counsel first.

The eShram Deadline You Might Have Already Missed

Aggregators had until 21 June 2026 to onboard their existing workers onto eShram. That deadline has already passed. The government notified the Social Security (Central) Rules on 8 May 2026. A circular followed on 1 June. Aggregators then had roughly three weeks to complete onboarding and API integration with the portal, per DLA Piper’s tracking of the mandate.

What hasn’t passed, and won’t, is the ongoing duty. Under Rule 48, aggregators must register new workers in real time or daily. They also have to report exits the same way and submit monthly updates through the designated portal. Miss the original window and you’re not off the hook, you’re just late. Non-compliance exposes an aggregator to penalty proceedings under Section 133. Treat it as overdue, not optional, and close the gap before the next filing cycle.

What the Contribution Rule Will Cost Gig and Platform Workers in India

The registration duty is live, but the money side of the rule hasn’t switched on yet. Section 114(5) of the code requires a separate notification to activate the actual social security contribution. As of this writing, the government still hadn’t issued that notification, or set the exact contribution rate. Budget for it anyway, since the structure is already written into law.

Once notified, aggregators will owe between 1 and 2 percent of annual turnover, net of certain central taxes and cesses, toward gig worker social security. A second ceiling caps that contribution at 5 percent of the amount actually paid to gig and platform workers. Whichever figure is lower is what applies. On top of that, the code sets an annual filing rhythm. A provisional return, Form XX, is due by 30 June. A final return, Form XXI, is due by 31 October. Late or short payments carry 1 percent monthly interest.

Comparing Engagement Models Once the Rule Bites

The table below lines up how three common engagement models sit relative to this shift. It’s not exhaustive, but it’s a useful gut check before you assume your current setup is fine as is.

Dimension	Aggregator-Engaged Gig Worker	Independent Contractor (Non-Aggregator)	EOR-Employed Staff
Legal recognition	Defined and tracked under the code	Governed by contract law, not the gig worker provisions	Full employee under Indian labour law
eShram registration duty	Mandatory, real time or daily	None	Not applicable, covered by EPFO and ESIC instead
Statutory contribution	1-2% of turnover, capped at 5% of worker payments, once notified	None directly, but misclassification risk rises	PF, gratuity, and other statutory benefits, built into payroll
Who carries audit risk	The aggregator platform	The hiring company, if the relationship looks like employment	Shared with the EOR provider, who owns the compliance record

Why This Matters Even If You’re Not an Aggregator

Regulators built the gig worker framework around a control-and-dependence test. That same test shows up in ordinary contractor misclassification disputes too. The factors are the same either way: who sets the schedule, who owns the tools, how continuous the work is, and whether the worker depends on one source of income. We’ve covered what misclassification actually costs employers in India in more depth. The gig worker code is more evidence that the line between “contractor” and “employee” is getting sharper, not softer.

Companies that got into the habit of calling long-term India-based workers “contractors” to skip payroll setup are the ones most exposed here. The government now has a live portal that tracks exactly this kind of relationship at scale. Even if your arrangement sits outside the aggregator definition today, the compliance direction is unmistakable.

What to Do Before the Next Deadline Lands

Four moves matter most right now. Start with a straight answer to one question: does any part of your India operation connect multiple workers to multiple clients or users through a platform, app, or internal marketplace? If yes, get local counsel to confirm your aggregator status. Complete eShram onboarding immediately, rather than waiting for the contribution rate to force the issue.

• Audit every India-based “contractor” relationship against the control-and-dependence factors, not just the label on the contract.
• Build the 1-2%-of-turnover contribution into next year’s budget now, even before the rate is formally notified.
• Set a calendar reminder for the Form XX and Form XXI filing dates if you do qualify as an aggregator.
• Compare the ongoing admin load of self-managed compliance against handing India-based hiring to an employer of record.

For roles that don’t need to sit inside a gig or marketplace structure at all, moving to a properly employed setup through an EOR removes the registration, reporting, and contribution questions altogether. The EOR carries that statutory burden as the legal employer instead. We’ve laid out how that comparison plays out in our EOR vs contractor model breakdown. And if you’re weighing this alongside broader India hiring questions, our guide to the 50 questions employers ask before hiring in India covers the rest, from entity setup to termination rules.

The Next Step Is an Audit, Not a Wait-and-See Approach

Don’t wait for the contribution rate notification to decide whether this applies to you. Run the aggregator test against your actual India operations this quarter. Close any eShram registration gaps now, while the penalty exposure is lower than it will be later. Reassess every long-standing “contractor” relationship too, using the same control-and-dependence test the government now enforces. That audit costs a few hours. Getting caught unregistered after the next filing cycle costs a lot more.