Aggregator Compliance India 2026: Gig Workforce Rules

India's gig economy has moved from informal to formally regulated. With the Code on Social Security, 2020 in effect since 21 November 2025, businesses that engage gig or platform workers now face specific, quantified compliance obligations — not general guidance, but a defined contribution formula with a legal cap and enforcement mechanism.

This guide explains what qualifies a business as an "aggregator" under Indian law, exactly how the contribution formula works, what benefits gig workers now receive, and what happens when compliance fails.

Quick Answer: What Is Aggregator Compliance Under India's Social Security Code?

Under Section 114 of the Code on Social Security, 2020, businesses classified as "aggregators" — digital intermediaries connecting service providers with customers — must:

1. Contribute between 1% and 2% of annual turnover to a Social Security Fund for gig and platform workers, as notified by the Central Government

2. Keep this contribution capped at 5% of the total amount paid or payable to gig and platform workers in that financial year

3. Register every gig worker with a Universal Account Number (UAN), linked to Aadhaar

4. Maintain accountability for contributions even when workers are managed through vendors

This applies regardless of company size — there is no exemption for startups or small businesses engaging gig workers.

Who Qualifies as an Aggregator Under Indian Law?

The Code on Social Security defines an aggregator as a digital intermediary or marketplace connecting a buyer or user of a service with a seller or service provider. Schedule 7 of the Code classifies aggregators into specific categories, including:

• Ride-sharing services

• Food and grocery delivery services

• E-marketplaces

• Logistics and fleet-based platforms

• Content and media services engaging gig-based creators

• Professional and freelance services platforms

You likely fall under this classification if your business:

• Engages gig or platform workers directly or through vendors

• Manages on-demand or task-based services through a digital platform

• Pays workers digitally, regardless of whether payment flows directly or through an intermediary

• Operates a fleet, marketplace, or service platform connecting workers to customers

There is no exemption based on company size. Startups, SMEs, and large enterprises engaging gig workers are equally covered under the Code.

Why This Matters Now: The End of Informal Gig Employment

Before the Social Security Code, gig and platform work existed in a regulatory gap — workers weren't formally recognized as employees, and businesses weren't required to contribute toward their social security.

This created what's sometimes called "shadow employment": a workforce performing regular, platform-directed work without the protections typically associated with formal employment.

The Code on Social Security changes this in three specific ways:

• Gig and platform workers are legally defined and recognized as distinct categories, separate from traditional employees but still entitled to specified social security benefits

• Aggregators are required to contribute financially toward a dedicated fund supporting these workers, rather than treating the relationship as purely transactional

• Compliance is intended to be digitally monitored through worker registration and contribution tracking, rather than relying on self-reporting alone

Practically, this means aggregators are no longer just facilitating transactions between workers and customers — they carry a defined financial and administrative obligation toward the workers using their platform.

For a broader overview of all four Labour Codes and their combined payroll impact, see our India Labour Codes 2026 guide.

The Turnover Contribution Rule, Explained

This is the requirement founders and CFOs need to understand precisely, since it's tied directly to company financials rather than headcount.

How the Contribution Is Calculated

Under Section 114(4) of the Code on Social Security, 2020, the contribution rate is:

• Not less than 1%, and not exceeding 2%, of the aggregator's annual turnover, at a rate to be notified by the Central Government

• Capped at 5% of the total amount paid or payable by the aggregator to gig and platform workers in that financial year — whichever is lower between the turnover-based calculation and this cap

• Calculated on annual turnover excluding any tax, levy, or cess paid or payable to the Central Government

Illustrative Contribution Scenarios

The table below illustrates how the contribution formula might apply at different business sizes. These are illustrative calculations based on the statutory formula — not official figures — and actual contribution rates depend on the specific percentage notified by the Central Government within the 1–2% range.

Important: The exact contribution percentage within the 1–2% range is set by Central Government notification, not fixed by the Code itself. Businesses should confirm the currently notified rate rather than assuming the midpoint, and should calculate the 5% cap based on actual gig-worker payouts, since this may result in a lower liability than the turnover-based calculation.

For the official contribution formula and current notifications, refer to Section 114 of the Code on Social Security, 2020.

ESIC and EPF Benefits Now Available to Gig Workers

India's social security framework, as extended under the 2026 rules, provides gig and platform workers access to benefits historically limited to traditional employment structures.

Health and Accident Coverage (ESIC-Linked)

• Medical and accident-related benefits

• Eligibility structured around platform engagement rather than traditional employer-employee status

• Coverage tracked through the digital compliance system tied to worker registration

Retirement and Pension Support (EPF-Linked)

• Designed to accommodate gig work's variable income pattern, without requiring a fixed salary structure

• A flexible contribution model rather than the fixed percentage structure used for traditional employees

• Intended to provide gig workers a path toward the same category of retirement benefits available to formal employees

UAN Mapping: Why Digital Identity Compliance Is Mandatory

Every gig worker must be mapped to a Universal Account Number (UAN), linked to their Aadhaar, to receive benefits under this framework.

Why This Registration Requirement Exists

• Enables benefit portability — a worker who moves between platforms retains their benefit history rather than starting over with each new aggregator

• Prevents duplicate registrations across multiple platforms, which would otherwise complicate contribution tracking and benefit eligibility

• Supports audit transparency — regulators can trace contributions and benefits to a specific worker rather than relying on platform-reported aggregates alone

For eligibility specifics, note that SS Rules generally require a gig or platform worker to have been engaged with an aggregator for a minimum continuous period within the relevant financial year — businesses should verify current eligibility thresholds directly with official sources, since these details are subject to rule notifications.

Principal Employer Liability: Why Using Vendors Doesn't Remove Risk

A common misconception is that routing gig workers through a vendor or contractor shifts compliance responsibility away from the platform itself. Under the Code's framework, this isn't the case.

What Happens If a Vendor Fails to Contribute

• The principal employer (the aggregator) can be held responsible for the shortfall, even when a vendor managed the actual worker relationship

• Penalties may be imposed directly on the aggregator, not solely on the non-compliant vendor

• Vendor-side explanations for non-payment don't automatically absolve the aggregator of liability

Practical Compliance Controls to Reduce This Risk

• Require documented proof of contribution from vendors before processing vendor payments

• Build verification checkpoints into invoice approval workflows, rather than processing vendor invoices without contribution confirmation

• Maintain centralized visibility into vendor compliance status rather than tracking this manually across multiple vendor relationships

Manual Compliance Tracking vs. Automated Systems

The core risk in manual tracking isn't necessarily non-compliance intent — it's the operational difficulty of accurately calculating and documenting contributions across a variable, turnover-linked formula without a system built for that specific calculation.

Why This Requires Purpose-Built Software, Not Generic Payroll Tools

Standard payroll software is generally built around fixed salary structures, standard deductions, and traditional employment relationships. Aggregator compliance introduces requirements that don't fit this model cleanly:

• Variable, turnover-linked contribution calculations rather than a fixed percentage of individual salary

• Vendor-layer compliance tracking, since many aggregators engage gig workers through intermediaries rather than directly

• UAN-based worker registration tied to a government identity system, rather than standard employee ID management

• Contribution reporting structured around aggregator-specific regulatory requirements, not standard payroll compliance reports

Businesses evaluating HRMS platforms for gig-workforce compliance should specifically confirm whether the platform handles turnover-based contribution calculations and vendor compliance tracking, rather than assuming standard payroll compliance features cover this requirement. For a broader look at statutory payroll obligations in India, see payroll compliance requirements in 2026.

Best Practices for Aggregator Compliance

Confirm your currently notified contribution rate. Since the exact percentage within the 1–2% range is set by government notification, verify the current rate rather than relying on outdated figures.

Calculate both the turnover-based amount and the 5% cap. Apply whichever produces the lower liability, since the cap is designed to protect against disproportionate contribution relative to actual gig-worker payouts.

Build vendor contribution verification into your payment workflow. Don't release vendor payments without confirmed proof of their contribution compliance, since liability can pass back to you regardless.

Register workers for UAN promptly during onboarding. Delayed registration can create gaps in benefit eligibility and complicate audit documentation later.

Monitor official notifications regularly. Contribution rates, eligibility thresholds, and procedural rules are subject to ongoing notification by central and state governments as implementation continues.

Final Thoughts

Aggregator compliance under India's Code on Social Security introduces a genuinely new financial and administrative obligation for platforms engaging gig and platform workers — a turnover-linked contribution formula, mandatory UAN-based worker registration, and liability that extends through vendor relationships rather than stopping at them. The businesses most exposed to compliance risk aren't necessarily those ignoring the requirement intentionally, but those attempting to track a variable, turnover-based obligation using tools built for fixed-salary payroll.

Want to see how ZFour HRMS supports gig-workforce and vendor compliance tracking?
Book a ZFour HRMS demo.