For platform aggregators, on‑demand logistics networks, and quick‑commerce operations in India, managing a tech‑enabled fleet is a core element of daily business. With the formal enforcement of the Code on Social Security, 2020 and the Social Security (Central) Rules, 2026 notified on 8 May 2026, the compliance landscape for the gig economy has fundamentally changed.
At the centre of this transformation is an immediate regulatory directive: the Ministry of Labour & Employment has mandated a strict deadline of 22 June 2026 for all digital aggregators to synchronise their live worker databases with the central e‑Shram portal via automated API integrations.
This policy change introduces a vital operational question that delivery partners, HR departments, and platform operations leads are actively working to resolve: Who decides how a gig worker‘s active days are tracked across competing digital networks, and how does the statutory 90/120‑day rule apply to individuals splitting their time across multiple applications?
The Executive Context: India‘s Evolving Welfare Floor
For years, the legal status of India‘s rapidly growing gig workforce remained undefined. Delivery partners, ride‑hailing drivers, and freelance operators existed outside traditional labour definitions, leaving platforms exempt from regular employee benefit contributions.
The implementation of the Code on Social Security, 2020 establishes a foundational welfare floor; extending legal recognition and targeted welfare benefits (such as accident insurance, health coverage, and old‑age protection) to gig and platform workers for the first time.
The Social Security (Central) Rules, 2026 now provide the procedural framework required to implement the Code in practice. To keep the system manageable and prevent temporary or single‑day log‑ins from diluting the welfare pool, the Rules introduce a clear eligibility filter known as the 90/120‑Day Rule:
- Single‑Platform Cap: A gig worker must be actively engaged with a single aggregator for at least 90 days in a financial year to qualify for state‑notified benefits.
- Multi‑Platform Track: For workers balancing multiple platforms, the eligibility threshold shifts to a minimum of 120 cumulative days across all platforms within the financial year.
Conversational Breakdown: Who Counts the Days and How?
To explain how the government tracks a mobile workforce switching between apps on a single smartphone, consider the mechanism of an electronic ledger system.
The state does not track location coordinates or application usage metrics directly. Instead, the tracking relies on a shared data link. Every registered aggregator is legally required to upload a digital summary of its partners‘ active periods to the e‑Shram portal on a quarterly baseline, using each worker‘s unique Universal Account Number (UAN). New worker registrations must be done in real time or on a daily basis.
This introduces two distinct rules regarding how a worker‘s active days are officially logged:
1. The “Income Earned” Rule
Under Rule 48 of the Social Security (Central) Rules, 2026, an individual is considered “engaged” with an aggregator for one day only if they earn income on that specific calendar day, regardless of the amount.
The Waiting Time Dilemma: Simply opening an app, waiting in a delivery zone, and logging off without completing a task or ride does not count toward the 90‑ or 120‑day thresholds. The system requires an income‑generating transaction to log a valid engagement day.
2. The Multi‑Aggregator Cumulative Multiplier
What happens if a delivery partner splits time across three major apps and completes exactly 100 calendar days of total work? Their eligibility depends entirely on whether their shifts overlapped on the same days.
The Rules calculate multi‑platform days cumulatively:
The Rules confirm that if a worker is engaged with multiple aggregators on the same calendar day, each engagement counts separately.
Dual‑Regime Analysis: The New Compliance Framework
Because labour is a Concurrent Subject under the Indian Constitution, platform operators must monitor both centralised data integration standards and emerging state‑specific welfare rules (such as specialised gig insurance programmes enacted in regions like Karnataka and Rajasthan).
| Compliance Vector | The Legacy Regime (Pre‑2025 Framework) | The Active Regime (2026 Notified Rules) |
| Legal Worker Classification | Excluded from primary labour acts; grouped loosely as independent contractors. | Formally recognised as Gig/Platform Workers under Section 2(35) of the Social Security Code. |
| Data Architecture | Decentralised internal spreadsheets managed independently by platforms. | Mandatory API integration with the central e‑Shram portal to generate a Universal Account Number (UAN). |
| Aggregator Financial Burden | No statutory welfare contribution requirements. | Mandatory contribution of 1% to 2% of annual platform turnover (rate to be notified by the Central Government), capped at 5% of worker payouts. |
| Non‑Compliance Penalties | Standard contractual or civil disputes. | 12% annual interest penalty (1% per month) for delayed social security fund contributions. |
2026 Core Impact Filters: The Strategic Platform Outlook
The compliance landscape for digital platforms extends beyond database integration, interacting directly with core structural filters embedded across the modern labour codes:
Separation from Traditional Salary Rules
Because gig workers operate outside a traditional employer‑employee relationship, they are exempt from the 50% Wage Rule and the 48‑Hour Exit Rule that govern standard company payrolls.
The Onboarding Verification Filter
To prevent data synchronisation errors before the upcoming government deadline, platforms must verify that every delivery partner or driver above 16 years of age undergoes Aadhaar‑seeded self‑declaration on the e‑Shram portal. Failing to link a partner‘s active days to a verified UAN can impact their eligibility and signal data friction to regulatory inspectors.
The Contractor/Fleet Loophole Barrier
The Rules explicitly cover not just the platform itself but associate companies, holding companies, subsidiaries, limited liability partnerships, and third parties. Platforms cannot bypass social security liabilities or data reporting duties by outsourcing delivery operations to local logistics intermediaries; the ultimate data compliance requirement remains firmly with the parent platform.
The 45‑Day Registration Mandate
Aggregators must upload all currently engaged worker details to the central portal within 45 days of the Rules coming into force (i.e., by 22 June 2026). New appointments and exits require real‑time or daily registration.
Core Compliance Checklist for Platform Management – FREE
To avoid statutory interest penalties and maintain operational continuity ahead of the government‘s integration deadlines, your compliance and engineering teams should execute this structured checklist:
- Complete API Synchronisation: Establish and validate the real‑time or quarterly data flow linking your platform‘s active delivery ledger with the e‑Shram portal before the 22 June 2026 enforcement cutoff.
- Automate UAN Collection: Embed a mandatory digital verification step into your partner onboarding app, requiring new gig workers to input or auto‑fetch their verified e‑Shram Universal Account Number (UAN).
- Configure the “Income Earned” Metric: Update your data tracking algorithms to ensure active days are logged strictly based on daily completed orders or transactions where earnings are recorded, filtering out inactive app log‑in hours.
- Set Up Turnover Contribution Reserves: Configure your financial systems to calculate and reserve the mandatory 1% to 2% of annual platform turnover (at the rate to be notified by the Central Government) for timely transfer to the Central Gig Workers Social Security Fund.
- Implement Real‑Time Reporting: Ensure new appointments and worker exits are registered on the central portal on a real‑time or daily basis as required under the Rules.
- Maintain Worker Engagement Records: Keep accurate records of each worker‘s engagement days, including income earned across multiple aggregators, to support eligibility verification.
Financial and Operational Risk Analysis
The financial risks of mismanaging gig worker compliance or failing to meet data synchronisation deadlines are significant for modern tech platforms:
Statutory Interest Realisation
Under the notified Rules, any platform that fails to calculate or transfer its mandatory social security turnover contribution on time faces an automatic 12% annual interest penalty (1% per month) on the delayed amount.
Account Deactivation Friction
If a platform fails to update its partners‘ active days accurately, those workers may lose access to state health and accident insurance covers. The Rules state that in the absence of regular updation, a gig worker may not be eligible to avail benefits under the Code. This can lead to increased partner churn, delivery downtime, and significant organisational friction during periods of high consumer demand.
The Third‑Party Vendor Exposure
Because the central framework holds the primary aggregator responsible for all partners on its system, any failure by an outsourced logistics vendor to maintain clean records will flow directly up the chain, exposing the parent tech entity to regulatory scrutiny and public accountability challenges.
Data Synchronisation Risks
While the 22 June 2026 deadline for API integration carries its own compliance urgency, the primary enforcement mechanism for data‑related defaults is that workers may become ineligible for benefits, rather than a direct financial penalty on the aggregator. However, this creates significant operational and reputational risk.
Conclusion
The 90/120‑day rule under the Social Security (Central) Rules, 2026 represents a paradigm shift for India‘s gig economy. For the first time, platform workers gain statutory recognition and a pathway to social security benefits but eligibility depends on accurate, real‑time tracking of engagement days across potentially multiple aggregators.
Platform aggregators face three core obligations:
- Data integration – API synchronisation with the e‑Shram portal by 22 June 2026
- Financial contribution – 1% to 2% of annual turnover (subject to government notification) to the Social Security Fund
- Real‑time reporting – Daily or real‑time registration of appointments and exits
Failure to comply triggers 12% annual interest penalties on delayed contributions and risks rendering workers ineligible for benefits creating both financial exposure and operational friction in a competitive labour market.
Smart platforms will:
- Automate UAN collection during onboarding,
- Configure engagement tracking based on income‑earned logic,
- Set up financial reserves for turnover‑based contributions,
- Implement real‑time reporting systems for worker movements, and
- Ensure third‑party fleet vendors are contractually bound to comply with data reporting obligations.
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 an 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.