For platform aggregators, on‑demand quick‑commerce networks, and corporate HR compliance heads, navigating the operational landscape of the Code on Social Security, 2020 has become a primary operational priority. Following its formal enforcement with the Social Security (Central) Rules, 2026 (notified on 8 May 2026), digital platforms face a strict compliance pipeline to synchronise their delivery fleets and freelance workforces with the central ecosystem.
Among the various operational questions facing CFOs and platform operations directors, a highly specific infrastructure concern has emerged: Is the new social security fund for gig workers a separate financial pool, or does it merge directly with the Employees‘ State Insurance (ESI) fund? When an eligible gig worker requires medical care, do they access traditional ESI hospitals, or are they routed to a completely new, untested infrastructure?
If your operations team assumes that the turnover levy is simply poured into the standard ESI registry, your financial modelling and compliance reporting are likely misaligned. Let’s look beneath the surface of the unified digital returns to map out exactly how the funds are partitioned, where workers may receive medical care, and how platforms can manage their statutory exposures.
The Executive Context: Tracking the Architecture of the Funds
To manage statutory risks effectively, an enterprise must first understand that the new framework creates a clear, legal distinction between traditional payroll insurance and platform‑based welfare levies. The code does not merge gig worker welfare contributions into the conventional ESI pool.
1. The Traditional Pool: Employees‘ State Insurance Corporation (ESIC)
The core ESI fund remains a strictly contributory payroll‑based insurance system under Section 4 of the Code. It is funded by traditional payroll deductions; specifically, a 3.25% employer contribution and a 0.75% employee contribution calculated against regular salaries.
This framework applies exclusively to regular employees, contract workers, and Fixed‑Term Employment (FTE) personnel earning up to the current statutory wage ceiling of ₹21,000 per month (₹25,000 for persons with disability). This fund operates entirely within an explicit employer‑employee relationship matrix.
2. The New Unified Pool: The Social Security Fund (Section 141)
Contrary to what some industry discussions suggest, the Code creates a single, unified Social Security Fund under Section 141 that covers unorganised workers, gig workers and platform workers together. The sources of this fund include:
- Contributions received under Section 109(3) (relating to schemes for unorganised workers)
- Contributions received under Section 114(3) (the aggregator turnover levy for gig and platform workers)
- Money collected from composition of offences under the Code
- Funding from any other social security fund established under any other central labour law
A separate account is maintained within the fund for each source of funding, ensuring that moneys are expended only for the purposes for which they were collected. For the welfare of unorganised workers at the state level, Section 141(5) empowers State Governments to establish their own Social Security Funds, funded by composition of offence moneys and such other sources as may be prescribed.
Comparison of Worker Coverage and Funding Sources
| Pool | Legal Basis | Covered Workers | Primary Funding Source |
| ESI Fund | Section 4 | Regular employees, contract workers, FTEs earning up to ₹21,000/month | Employer (3.25%) + Employee (0.75%) |
| Employees’ Provident Fund (EPF) | Chapter III | Regular employees in establishments with 20+ workers | Employer + Employee monthly contributions |
| Social Security Fund | Section 141 | Unorganised workers, gig workers and platform workers | Aggregator turnover levy (1‑2%), government funding, composition of offence moneys |
Where Do Workers Go for Medical Care? The Current Status (2026)
The separation of financial pools naturally raises the question: If the funds do not mix, does the government need to construct an entirely new network of hospitals for app‑based delivery fleets?
The answer is more complex, and the healthcare delivery mechanism is not yet finalised.
The Ayushman Bharat Integration – Not Yet Operational
While some industry discussions have pointed to a potential integration with the Ayushman Bharat‑Pradhan Mantri Jan Arogya Yojana (AB‑PMJAY) network, official sources confirm that no final decision has been taken by the government. ESI authorities invited public suggestions on extending medical benefits to gig and platform workers in early 2026, but an RTI query filed on June 1, 2026, revealed that the Social Security Cell of the Ministry of Labour is still deliberating the healthcare delivery mechanism. A formal government notification has not yet been issued.
Aggregators should not represent to their workers that Ayushman Bharat benefits are available through e‑Shram registration until a formal notification is published by the Ministry of Labour.
Service‑Level ESIC Infrastructure Sharing – Permitted but Not Yet Activated
While the funds remain separate, Section 141(4) of the Code grants the National Social Security Board the authority to administer the fund for specified purposes, including medical facilities. This legally permits inter‑agency service‑level arrangements that could allow the government to utilise specific ESIC medical centres and dispensaries for gig workers, with costs funded directly by the independent Gig Workers’ Social Security Fund.
However, no gazette notification or board resolution has been issued publicly confirming such arrangements. These remain potential implementation pathways, not active service delivery channels.
What This Means for Aggregators
Platforms should:
- Not promise healthcare benefits to gig workers beyond what is legally confirmed in official notifications.
- Monitor Ministry of Labour notifications closely for updates on the healthcare delivery mechanism.
- Ensure their compliance returns (Form‑XXI) are filed accurately, regardless of the status of healthcare delivery.
Legacy Framework vs. Evolving Social Security Code
| Aspect | Legacy Regime (Pre‑Code) | Modern Code Regime (2026) |
| Legal definition | No formal definitions for gig/platform workers. | Formal recognition under Section 2(35) of the Social Security Code. |
| ESI fund access | ESIC benefits strictly reserved for formal payroll employees. | Traditional ESI fund remains separate; gig workers do not access ESIC registry. |
| Gig worker fund | Non‑existent. | Unified Social Security Fund under Section 141 established. |
| Healthcare delivery | No safety net. | Not yet finalised – ESI authority invited suggestions; Ministry still deliberating. No final notification issued. |
| Aggregator contribution | Zero statutory liability. | Mandatory 1‑2% of annual turnover (excluding taxes) under Section 114(4), capped at 5% of worker payouts. |
2026 Core Impact Filters for Corporate Restructuring
When executing an internal compliance audit of your workforce layout this year, HR and legal teams must evaluate how gig worker mechanisms interact with broader corporate payroll filters.
Isolation from the 50% Wage Rule
Traditional company payrolls must satisfy the strict 50% Wage Rule under the Code on Wages, 2019, which mandates that basic salary plus dearness allowance constitute at least 50% of an employee‘s total gross CTC. Because gig workers operate under dynamic, task‑based transaction fees rather than structured corporate salary components, they remain exempt from this allocation rule.
Caution: If a platform guarantees a fixed monthly sum, provides regular allowances, or structures payments to mirror a traditional salary slip, courts can apply the “control test” or “integration test” derived from Supreme Court precedents (e.g., Bangalore Water Supply and Sewerage Board v. R. Rajappa, 1978) to re‑classify gig workers as “employees,” retroactively triggering the 50% Wage Rule and associated obligations.
Exemption from the 48‑Hour Exit Rule
Section 17 of the Code on Wages, 2019 enforces a strict 48‑Hour Exit Rule, requiring all full‑and‑final (F&F) settlements for regular employees to be paid within 2 working days of separation. While routine account deactivations for gig fleets do not trigger this rapid 2‑day corporate payout mandate, platforms must still ensure that all final transactional earnings are processed transparently via the app interface to avoid contract disputes before State Welfare Boards.
The Reclassification Risk Protection
If an aggregator fails to onboard its delivery partners via the e‑Shram portal using verified Universal Account Numbers (UANs), or attempts to execute regular monthly deductions that mimic a standard salary slip, courts can look past the vendor paperwork. By applying established judicial tests for determining employment relationships, a court can reclassify those gig partners as direct employees, triggering retroactive liabilities for both standard ESIC contributions and pro‑rata gratuity dues.
Core Compliance Checklist for Platform Aggregators – FREE
To protect your enterprise against statutory interest penalties and maintain clean electronic compliance returns, ensure your operations desk executes this checklist:
- Separate the Financial Accounting: Ensure your corporate treasury tracks and handles the 1‑2% annual turnover contribution as a distinct operational overhead, completely separate from your internal corporate ESIC payroll software lines. Under Section 114(4), this contribution shall be at such rate not exceeding two per cent, but not less than one per cent, as may be notified by the Central Government.
- Enforce Aadhaar‑Seeded UAN Collection: Update your fleet onboarding application to mandate that every delivery partner inputs or auto‑verifies their e‑Shram Universal Account Number (UAN) before executing their first order. New appointments must be registered on a real‑time or daily basis under the Social Security (Central) Rules, 2026.
- Verify the 5% Payout Limit: Configure an automated ledger check to ensure that your annual turnover‑based social security fund transfers consistently stay within the statutory 5% cap of total worker payouts. The proviso to Section 114(4) clearly states: “Provided that the contribution by an aggregator shall not exceed five per cent. of the amount paid or payable by an aggregator to gig workers and platform workers”.
- File Form‑XXI Annually: Aggregators must file Form‑XXI with the National Social Security Board annually, certifying compliance with the contribution framework.
- Update Vendor Master Service Agreements: Review all contracts with third‑party logistics intermediaries or local fleet suppliers to ensure they maintain identical data transparency standards; parent aggregators remain directly liable for any indirect onboarding lapses.
- Monitor Ministry Notifications: Track official notifications from the Ministry of Labour & Employment regarding the final healthcare delivery mechanism for gig workers. Do not promise benefits until confirmed. Also note that under Section 114(5), the date of commencement of contribution from aggregator under this section shall be notified by the Central Government.
Financial and Operational Risk Analysis
The operational risks of mismanaging gig worker social security data extend far beyond simple human resource friction:
| Risk Category | Operational Implication | Legal & Financial Payout |
| Delayed Contribution Levy | Failing to calculate or deposit the turnover contribution within statutory timelines. | Automatic 12% annual interest penalty (1% per month) under central return rules. |
| Onboarding Linkage Failures | Deploying fleet partners whose active days are not synchronised with the central e‑Shram API before the June 22, 2026 deadline. | Automated flags in unified electronic returns, leading to targeted labour inspections. |
| Mismanaged Payout Deductions | Attempting to pass the corporate turnover levy down as a direct deduction from worker earnings. | Class‑action disputes before State Welfare Boards; potential orders for complete restitution of back‑earnings. |
| Workforce Reclassification | Blurring contract terms to mirror traditional payroll structures (fixed monthly guarantees, allowances, salary‑style deductions). | Retroactive exposure to standard ESIC liabilities, 50% Wage Rule obligations, and pro‑rata gratuity rules. |
| Healthcare Delivery Unconfirmed | Representing to workers that AB‑PMJAY benefits are available through e‑Shram registration. | Potential consumer protection claims for misrepresentation; regulatory scrutiny for misleading communications. |
The Strategic Outlook
The Code on Social Security, 2020, has fundamentally restructured India‘s social security landscape for gig and platform workers. The financial architecture is clear: contributions flow into a unified Social Security Fund under Section 141, with separate accounts maintained within the fund for different sources. The National Social Security Board, chaired by the Union Labour Secretary, oversees this framework.
However, the healthcare delivery mechanism; the most practically significant benefit for gig workers is not yet finalised. While the AB‑PMJAY network and ESIC infrastructure sharing remain viable pathways under consideration, aggregators must await formal government notification before incorporating any healthcare benefit promises into their worker communications or onboarding materials.
Treating employee welfare as a dynamic, strategic operational priority rather than a basic administrative checklist protects your board of directors from personal statutory exposure. By ensuring your data infrastructure maps accurately to the unified framework of the modern codes, your company can maintain flexible operations while building long‑term institutional value.
Disclaimer – This publication is provided for general informational and educational purposes only and does not constitute legal advice. The information contained herein may not reflect the most current legal developments and is not guaranteed to be complete, accurate, or up‑to‑date. Nothing in this publication creates a lawyer‑client relationship between the reader and the author or publisher. Laws, regulations, and judicial interpretations vary by jurisdiction and may change over time. Readers should not act or refrain from acting on the basis of any information contained in this publication without first seeking independent legal counsel from a qualified lawyer licensed to practice in the relevant jurisdiction. The author and publisher expressly disclaim all liability in respect of any actions taken or not taken based on any or all of the contents of this publication. Case citations and statutory references are provided for illustrative purposes only and do not constitute a guarantee of any particular outcome. Always consult a qualified legal professional for advice tailored to your specific circumstances.