The Code on Social Security, 2020 formally recognizes 'gig workers' and 'platform workers' as distinct categories — separate from both traditional employees and independent contractors — and creates a social security framework specifically for them, funded substantially by the aggregators and platforms that engage this workforce. For any business built around a gig or platform-based workforce model — delivery, ride-hailing, freelance marketplaces, home-services platforms — this is a direct compliance obligation, not a policy aspiration.
Who Counts as a Gig or Platform Worker
- A gig worker is defined broadly as a person who performs work outside a traditional employer-employee relationship, earning income from such activities.
- A platform worker is a person engaged in platform work — an arrangement outside a traditional employer-employee relationship, where organizations or individuals use an online platform to access other organizations or individuals to solve specific problems or provide specific services in exchange for payment.
These definitions are deliberately distinct from 'employee' — meaning platforms don't need to reclassify their gig workforce as employees to fall within these obligations; the Code creates a parallel, purpose-built compliance track instead.
Employer (Aggregator) Obligations
1. Registration. Aggregators falling within specified categories (e-commerce, ride-sharing, food and grocery delivery, content and media services, professional and healthcare services delivered via platforms, and others as notified) need to register under the framework and register their gig/platform workers for social security benefits.
2. Contribution to the Social Security Fund. Aggregators are required to contribute a percentage of their annual turnover (or a specified amount per transaction, depending on the final contribution mechanism notified) toward a dedicated Social Security Fund for gig and platform workers — this is a genuine, ongoing cost obligation tied to platform revenue or transaction volume, not a fixed nominal fee.
3. Worker database maintenance. Aggregators need to maintain and periodically update records of the gig and platform workers engaged through their platform, feeding into a national database being built for this worker category, so that benefits can be tracked and delivered even as workers move between platforms.
4. Life and disability cover, health and maternity benefits, old-age protection. The specific benefit basket for gig and platform workers — administered through the Social Security Fund rather than through the traditional PF/ESI framework applicable to employees — is meant to give this workforce category access to benefits that were previously entirely absent for non-employee engagement models.
Practical Compliance Steps for Platforms
- Confirm applicability — determine whether the platform's business model and sector fall within the notified aggregator categories, since the obligation applies specifically to notified sectors, not to every business that engages any form of flexible or contract labour.
- Build worker registration into onboarding — capture the data points needed for the national gig-worker database as part of the platform's existing worker onboarding flow, rather than retrofitting this after the fact for an already-large existing worker base.
- Model the contribution cost into unit economics — since the contribution is linked to turnover or transaction value, this needs to be factored into pricing and take-rate models from a financial planning perspective, not treated as a compliance line item disconnected from the business model.
- Coordinate with payroll processing and employment functions, even though gig workers aren't on formal payroll — the contribution computation, worker database reporting, and benefit administration still needs a systematic internal owner, typically sitting alongside the payroll/HR function given the overlapping compliance calendar.
- Track state-specific gig worker welfare legislation separately — several states have introduced their own gig-worker welfare boards and cess/contribution mechanisms in parallel with the central Code, meaning a platform operating across multiple states may face overlapping or state-specific obligations that need to be reconciled, not assumed to be superseded entirely by the central framework.
Where Platforms Are Getting This Wrong
- Assuming this doesn't apply because workers are 'independent contractors' — the Code's gig/platform worker categories are specifically designed to capture this workforce model regardless of the contractual label used.
- Treating the contribution as a future obligation to plan for 'once fully notified' rather than tracking the actual state-wise and sector-wise notification timeline, which varies and is already active in some jurisdictions.
- Not building worker registration into onboarding systems early, creating a large backlog of historical worker data that needs to be reconstructed later for database compliance.
For any platform business with a gig or freelance workforce at its core, this is now a genuine compliance and cost-planning question — not a future regulatory risk to monitor from a distance, but an obligation that needs registration, contribution planning, and worker database systems built into the operating model now.
Perfect Accounting helps platform and aggregator businesses assess Code on Social Security applicability, model contribution costs, and build compliant gig-worker registration processes.