For years, a company engaging gig or platform workers in India operated in a legal grey zone. There was no statutory definition of a “gig worker,” no mandated employer contribution, and no formal registration system tying that work to any social security net. That changed with India’s Code on Social Security, 2020, and for global companies that rely on India’s gig and platform workforce, understanding what this Code actually requires is no longer optional homework; it’s a compliance question with real financial exposure attached.
What Changed, and Why It Took Five Years
The Code on Social Security, 2020 was one of four labour codes passed to consolidate India’s fragmented labour law framework, nearly 29 separate central statutes built for a traditional employer-employee relationship that never accounted for app-based work. The Code sat largely dormant for years while states and the central government worked through implementation details.
That changed on 21 November 2025, when all four labour codes were brought into force. The final Social Security (Central) Rules, 2026 were notified on 8 May 2026, updating the implementation position for gig and platform work.
Who Actually Counts as a “Gig Worker” Under the Code
This distinction matters more than it sounds. Under the Code, a gig worker is defined as someone who performs work or earns income outside a traditional employer-employee relationship. This is a deliberate legal distinction: the Code creates a framework for social-security protection for gig and platform workers while keeping them distinct from traditional employees under the Code.
For global companies, this separation is easy to get wrong. Fixed-term employment and gig/platform engagement are governed by entirely different frameworks under the Code, and the two should never be conflated in contracts or internal policy. Treating a gig arrangement like an employment contract, or vice versa, creates exposure on both sides of that line.
The Aggregator Contribution Requirement
The Code creates a financial contribution framework for specified aggregators. Under Section 114(4), aggregators falling within the categories listed in the Seventh Schedule are subject to a contribution rate that must be notified by the Central Government, within a range of 1% to 2% of annual turnover. The contribution is capped at 5% of the amount paid or payable to gig and platform workers. Annual turnover for this purpose excludes any tax, levy and cess paid or payable to the Central Government. Section 114(5) separately requires the Central Government to notify the commencement date for the contribution.
As of October 2026, no central notification specifying both the contribution rate and its commencement date appears in the official materials published so far. The statutory 1%-2% range should therefore not be presented as a fixed rate already payable in every case. The final Social Security (Central) Rules, 2026 prescribe self-assessment and return procedures in Forms XX and XXI, and Form XX includes a 5%-of-payments calculation option. Because Section 114(5) requires a separate notification of the commencement date, companies should read Rule 49 alongside the latest notifications before deciding whether a contribution is due or calculating an amount.
A few operational details matter here for compliance planning:
- The turnover figure used for the calculation excludes any tax, levy and cess paid or payable to the Central Government.
- Under the final Rules, any excess contribution claimed through Form XXI must be refunded electronically within 90 days of receipt of the claim.
- Where a contribution is due and is paid late, the Rules provide for interest at 1% for every month or part of a month until payment.
- Worker registration and reporting are separate obligations: aggregators were required to share details of existing gig and platform workers through the designated central portal within 45 days of the Rules commencing, and must register new engagements in real time or daily and update worker details as required.
Worker Eligibility Isn’t Automatic Either
The final Social Security (Central) Rules, 2026, notified on 8 May 2026, set an engagement threshold for eligibility for benefits under a scheme: a worker must have been engaged for at least 90 days with one aggregator, or 120 days across multiple aggregators, in the last financial year. Registration and any additional scheme-specific conditions also apply.
This creates a real gap between legislative intent and actual coverage. Given how fluid platform work tends to be, a meaningful share of India’s gig workforce may not clear that threshold in any given year, which means compliance for a company isn’t just about contributing to the fund, it’s about accurately tracking engagement days per worker to determine who’s even eligible.
Scale of What This Actually Covers
The size of the workforce this framework touches is part of why global companies should be paying attention now rather than later. India’s gig economy is estimated to have engaged 7 to 8 million workers as of 2020-21, and that number is projected to reach 23.5 million by 2029-30. Any company scaling a gig or platform workforce in India over the next few years is scaling directly into this compliance framework, not around it.
Gig Worker vs. Fixed-Term Employee vs. EOR-Employed Staff
| Category | Legal Status | Employer Obligations |
|---|---|---|
| Gig / platform worker | A distinct statutory category defined around work outside a traditional employer-employee relationship. | For an aggregator within the specified categories, registration and reporting duties apply. The contribution rate and start date are subject to the applicable notifications and rules; the Code also sets a 5% cap against payments to workers. |
| Fixed-term employee | Direct employee, pro-rata statutory benefits | Full statutory compliance (PF, ESI, gratuity where applicable) on a pro-rata basis |
| EOR-employed staff | Direct employee of the EOR, working for the client | The EOR can administer employment contracts, payroll and applicable benefits; responsibilities depend on the arrangement and the model does not automatically remove every client-side duty. |
What This Means for Global Companies
For a foreign company engaging India-based gig or platform workers, either directly or through a local aggregator relationship, the practical risk isn’t the contribution rate itself. It’s misclassification: treating what is functionally an employment relationship as gig work to avoid statutory obligations. As enforcement of the Code matures, that distinction is exactly where regulators are expected to look first.
Companies building a longer-term, more integrated India-based team, rather than a purely transactional gig relationship, often find that the compliance overhead of tracking eligibility thresholds, contribution calculations, and aggregator registration outweighs whatever flexibility the gig model offered in the first place. In those cases, engaging talent as formal employees through a compliant structure, such as an Employer of Record, sidesteps the ambiguity entirely: the worker is a direct employee with clear statutory entitlements, and the company isn’t left interpreting a still-evolving regulatory framework on its own.
Conclusion
The Code on Social Security marks the first time India has formally acknowledged gig and platform work in its labour law framework, but “formally acknowledged” isn’t the same as “fully resolved.” The final Central Rules now set out registration and eligibility requirements, while the contribution rate and commencement date remain subject to the relevant Central Government notifications. Companies should check the latest official position rather than assume that every part of the framework is operational in the same way. Understanding where the gig classification ends and formal employment begins is the first step to staying on the right side of a framework that’s only going to get more scrutinized from here.
FAQs
1. What is the Code on Social Security, 2020?
It’s one of four labour codes that consolidated India’s labour law framework and, for the first time, formally defines gig and platform workers and brings them into a statutory social security system.
2. Are gig workers now classified as employees in India?
No. The Code recognizes gig and platform workers as a distinct category with new social security entitlements, but they remain independent contractors rather than employees of the aggregator.
3. How much must aggregators contribute under the Code?
The Code sets a range of 1% to 2% of annual turnover for specified aggregators, capped at 5% of the amount paid or payable to gig and platform workers. The actual rate and its start date depend on Central Government notifications.
4. Do all gig workers automatically qualify for benefits?
No. The final rules require a minimum engagement of 90 days in a financial year with a single aggregator, or 120 days if the worker is engaged across multiple aggregators.
5. What’s the compliance risk for global companies using gig workers in India?
The main risk is misclassification, structuring what is functionally an ongoing employment relationship as gig work to avoid statutory obligations. As enforcement develops, this is expected to be a primary area of regulatory scrutiny.
