Social Security for Gig Workers: Complying with the Code on Social Security

Under the gig workers social security code framework within the Code on Social Security, 2020, businesses operating as digital aggregators must register their on-demand workforce on the central portal and contribute between 1% and 2% of annual turnover, capped at 5% of total payouts to gig and platform workers, to fund statutory welfare schemes.
India's digital economy has turned ride-hailing, quick commerce, logistics, and on-demand professional services into primary economic engines. For years, businesses engaged flexible talent through independent contractor models that operated outside statutory safety nets. The operationalisation of the Code on Social Security, 2020 introduces mandatory welfare contributions and legal recognition for flexible work arrangements. Finance and human resource leaders must now move beyond managing gig personnel as vendor accounts payable entries to ensure statutory audit readiness.
Understanding Aggregator Mandates Under the Gig Workers Social Security Code
The gig workers social security code establishes a dedicated statutory category under Chapter IX of the Code on Social Security, 2020. Prior to this legislation, Indian labour law recognized only formal employees, contract labour, or independent commercial vendors. The Code creates distinct definitions under Section 2 to bring digital intermediaries and on-demand personnel into a regulated welfare net without imposing the full overhead of traditional employment.
Section 2(35) defines a gig worker as someone earning outside a traditional employer-employee relationship. Section 2(60) defines platform work as an arrangement using an online platform to access organisations or individuals to solve specific problems or provide services for payment, while Section 2(61) defines a platform worker as an individual undertaking platform work. Platform workers are a digital subset of gig workers, whereas non-platform gig workers operate without an online intermediary.
Aggregator duties apply to entities defined under Section 2(1) and the Seventh Schedule, which covers nine categories: ride-sharing, food delivery, logistics, e-marketplaces, healthcare portals, travel booking, and professional services. If your business acts as a digital intermediary connecting buyers with individual service providers, you are an aggregator subject to Chapter IX obligations.
Distinguishing between traditional employees and gig workers is essential. Attempting to classify regular operational staff as gig workers to avoid statutory provident fund or gratuity payouts creates severe legal exposure. Indian labour authorities assess managerial control, supervision, and working restrictions over contractual labels.
The following decision tree illustrates how enterprises should evaluate worker engagements under the Code on Social Security:
flowchart TD
A["Evaluate Worker Engagement"] --> B{"Direct supervision or control?"}
B -- "Yes" --> C["Traditional Employee"]
C --> D["Apply EPF, ESI, Gratuity"]
B -- "No" --> E{"Digital platform intermediary?"}
E -- "Yes" --> F["Platform Worker"]
F --> G["Apply Chapter IX Aggregator Rules"]
E -- "No" --> H{"Piece rate task engagement?"}
H -- "Yes" --> I["Independent Gig Worker"]
I --> J["Apply Contractor Tax Rules"]
H -- "No" --> K["Unorganised Wage Worker"]The Statutory Funding Formula and Dual-Ceiling Mechanism
Section 114 of the Code governs welfare schemes for gig and platform workers, covering life and disability insurance, health and maternity benefits, accidental death cover, old age protection, and crèche facilities. The Central Government funds these schemes through a mix of government allocations, corporate social responsibility funds, and mandatory aggregator contributions.
Under Section 114(4), every qualifying aggregator must contribute between 1% and 2% of annual turnover, as notified by the government. Crucially, Parliament capped this contribution at 5% of the aggregate amount paid or payable by the aggregator to its gig and platform workers.
This dual-ceiling framework requires corporate finance teams to calculate two distinct figures each financial year:
- Turnover Threshold: 1% to 2% of annual aggregator turnover.
- Payout Ceiling: 5% of gross disbursements made to gig and platform workers.
The statutory liability is limited to whichever amount is lower. Consider two contrasting business models under an illustrative notified contribution rate of 1.5% of turnover:
| Metric | High-Turnover Platform | Asset-Light Marketplace |
|---|---|---|
| Annual Turnover | ₹1,000,000,000 (₹100 Cr) | ₹200,000,000 (₹20 Cr) |
| Disbursements to Gig Workers | ₹80,000,000 (₹8 Cr) | ₹120,000,000 (₹12 Cr) |
| 1.5% of Turnover | ₹15,000,000 (₹1.5 Cr) | ₹3,000,000 (₹30 Lakh) |
| 5% Cap on Payouts | ₹4,000,000 (₹40 Lakh) | ₹6,000,000 (₹60 Lakh) |
| Statutory Payable Amount | ₹4,000,000 (Payout Cap Bites) | ₹3,000,000 (Turnover Rate Applies) |
The high-turnover platform pays ₹40 lakh rather than ₹1.5 crore because the 5% payout ceiling acts as a statutory brake. In contrast, the asset-light marketplace pays based on turnover because 1.5% of turnover is lower than the 5% disbursement limit.
Registration Mandates and Portal Integration
Compliance under Chapter IX requires active worker lifecycle management. Section 113 stipulates that every unorganised worker, gig worker, and platform worker must register on the national database. The Ministry of Labour and Employment operationalises this through the e-Shram portal, which assigns a 12-digit Universal Account Number (UAN) seeded with Aadhaar.
Aggregators carry specific statutory duties under the Social Security (Central) Rules. Onboarding an on-demand worker requires digital verification of their e-Shram registration. If an incoming worker does not possess an active UAN, the aggregator must facilitate their self-declaration and digital enrollment before assigning billable tasks.
Aggregators must submit regular electronic records to the central portal detailing:
- Worker onboarding dates and identification credentials.
- Operational days logged by each worker during the period.
- Gross disbursements, incentive payments, and deductions processed.
- Exits, account deactivations, and contract terminations.
Tracking active days is essential because eligibility for specific central benefits requires a worker to have completed at least 90 days with a single aggregator, or 120 days across multiple aggregators, during the preceding financial year. Our guide on handling payroll for gig workers and freelancers outlines the necessary operational controls.
The operational sequence below highlights the statutory compliance flow for aggregators from onboarding through fund remittance:
flowchart LR
A["Onboard Worker"] --> B["Verify UAN and Aadhaar"]
B --> C["Track Tasks and Payouts"]
C --> D["File Quarterly Portal Data"]
C --> E["Calculate Dual Cap Contribution"]
E --> F["Compare Turnover Against Payouts"]
F --> G["Remit Social Security Fund"]Navigating Central Rules and State-Level Gig Worker Legislations
A major challenge for pan-India aggregators is managing central and state legislations simultaneously. While the Code on Social Security provides a national umbrella, several states have enacted independent laws to address immediate welfare demands.
Rajasthan enacted the Rajasthan Platform Based Gig Workers (Registration and Welfare) Act, 2023, establishing a state welfare board funded by a transaction-level cess between 1% and 2% per booking. Karnataka followed with dedicated platform worker legislation requiring registration, algorithmic transparency, contract clarity, and a state welfare fee. Jharkhand and Telangana have developed similar statutory frameworks.
These overlapping laws create two distinct operational challenges:
- Divergent Contribution Bases: The central Code assesses an annual turnover contribution capped at 5% of payouts, whereas state acts levy a per-transaction cess at the point of sale.
- Ledger Separation: Aggregators must establish rigorous accounting separations to ensure transaction fees collected for state funds do not inflate taxable corporate turnover or conflict with central fund remittances.
Engaging specialized Labour Codes Consulting helps businesses harmonize state cess collections with central obligations, preventing double deductions and audit exposure.
Critical Compliance Controls and Risk Mitigation
Complying with the gig workers social security code requires internal controls across operations, legal contracting, and payroll compliance accounting. Below are four primary pitfalls and how to avoid them:
1. Excessive Supervision and Deemed Employment Exposure
The legal boundary between an independent gig worker and an employee rests on behavioral control. Mandating strict shift hours, restricting workers from competing apps, or managing them through direct supervisors can lead labour authorities to reclassify them as regular employees. This triggers retrospective claims for statutory provident fund contributions under EPFO regulations, state insurance, and gratuity. Reviewing contracts against our guide to managing gig workers in India maintains clear boundaries.
2. Fragmented Payout Accounting
Because the contribution cap depends on total disbursements to gig workers, organizations must capture every financial flow: base task fees, surge bonuses, customer tips, fuel subsidies, and referral rewards. Incomplete ledgers can distort cap calculations, resulting in overpayments or non-compliance penalties under Section 133.
3. Data Privacy and DPDP Compliance
Registering gig workers on government portals involves collecting Aadhaar numbers, bank details, and geolocation data. Under the Digital Personal Data Protection Act, aggregators act as data fiduciaries. You must provide clear notice, capture explicit worker consent, and secure data pipelines.
4. Tax and Labour Record Mismatches
Aggregators deduct tax at source (TDS) under Section 194C or 194J on contractor payments monitored by the Income Tax Department. Discrepancies between payouts in quarterly TDS returns (Form 26Q) and figures submitted on the social security portal can trigger automated audits. Integrating tax and welfare reporting is essential.
How MYND Streamlines Gig Worker Social Security Compliance
Managing thousands of distributed gig workers across shifting state and central mandates requires scalable compliance infrastructure. At MYND, we combine over two decades of enterprise compliance experience with proprietary automation technology to help aggregators meet these requirements smoothly.
Our comprehensive Compliance Management Services and specialized labour advisory teams handle every stage of the gig worker lifecycle. We assist organizations with automated e-Shram onboarding verification, quarterly activity reporting, and transaction reconciliation. Our proprietary systems calculate the dual-cap formula dynamically across all operational entities, ensuring accurate provisioning without overpaying statutory fees.
Enterprises partnering with MYND achieve an average 35-40% cost reduction in compliance administration while maintaining 99% compliance achievement. With over 20 million transactions processed annually and 6 million payslips generated, our platforms ensure that your on-demand workforce remains fully protected, audit-ready, and aligned with India's evolving labour architecture.
Building a Sustainable Future for On-Demand Work
The introduction of social security for gig workers represents a fundamental maturation of India's labour ecosystem. Complying with the gig workers social security code is not merely a defensive legal exercise; it is a strategic investment in talent retention, brand trust, and operational resilience.
By establishing rigorous worker classification protocols, automating e-Shram onboarding, modeling the dual-cap contribution accurately, and preparing for overlapping state legislations, forward-thinking organizations can protect their operations from legal exposure. As enforcement accelerates, businesses that build reliable compliance systems today will secure a distinct advantage in managing on-demand talent.
Frequently Asked Questions
What is the contribution rate under the gig workers social security code?
Under Section 114(4) of the Code on Social Security, 2020, aggregators must contribute between 1% and 2% of annual turnover, as notified by the Central Government. This contribution is capped at 5% of the aggregate amount paid or payable to gig and platform workers during the financial year.
Does paying gig worker social security create an employer-employee relationship?
No. The Code explicitly distinguishes gig and platform work from traditional employment. Contributing to the Social Security Fund does not confer employee status, provided the aggregator avoids direct managerial control, rigid shift schedules, and exclusivity mandates.
How do aggregators verify a gig worker's e-Shram registration?
Aggregators verify workers via API integration with the central e-Shram portal using the worker's 12-digit Universal Account Number (UAN) and Aadhaar authentication. If an onboarding worker lacks an active UAN, the aggregator must facilitate their self-declaration before assigning tasks.
How do state gig worker laws interact with the central Code on Social Security?
State acts such as Rajasthan's Gig Workers Act operate alongside the central Code. While the central framework assesses an annual turnover contribution capped at 5% of payouts, state laws generally levy a transaction-level cess on individual bookings. Aggregators must maintain separate ledgers for both.
What are the penalties for non-compliance under Chapter IX of the Code?
Failure to register workers, report quarterly data, or remit mandatory contributions under Section 114 attracts monetary fines and penalties under Section 133 of the Code. Continued default can lead to compounded financial liabilities and formal legal proceedings before labour authorities.
Talk to a MYND specialist
Tell us a little about your setup. A specialist will come back within one business day.


