New Social Security Law for Gig Workers in India

India has formally brought gig and platform workers into its central social security net. That is good policy, but it also creates new HR and payroll work you must plan for now.

What changed and when

The Code on Social Security, 2020 recognizes gig and platform workers and puts them within a central social security framework. The government has now operationalized this for aggregators and platforms, with the effective applicability date set for 21 November 2025.

This means platform operators and certain aggregators will have to register covered workers and contribute to social security schemes designed for them. The official announcement is available here: official announcement.

As of 2026, employers and platforms should treat this as a near-term compliance program. The law sets the direction and the obligation. Your job is to get your worker data, contracts, and payment systems ready.

Who is covered and who pays

Covered persons. The framework targets gig and platform workers who earn by accepting tasks or services through a platform or similar arrangement, without a traditional employer-employee relationship.

Who is on the hook. Aggregators and platform operators will bear primary responsibility for registering eligible workers and making contributions into notified schemes for their welfare. The contribution is expected to be a small formula-driven amount linked to business volumes and payouts, to be detailed in rules and scheme notifications.

Important nuance. The law does not convert gig workers into employees. It creates a separate social security track for them. Traditional employee benefits like EPF and ESIC still apply to employees, not to genuine gig workers.

What is clear vs what is still unclear

What is clear today

• Gig and platform workers are within the central social security framework of the Code on Social Security, 2020.
• Registration and eligibility concepts have been defined, and platforms will be expected to onboard covered workers on the designated system.
• Aggregators will need to fund social security for covered workers once the specific schemes and collection mechanics are notified.

What remains unclear or pending detail

• The exact contribution formula, base, and caps for different categories of aggregators.
• Whether any part of the contribution may be contractually passed on or adjusted, and in what circumstances.
• The list of specific benefits to be delivered in the first phase, and the agency that will operate them.
• Integration flows and APIs for bulk registration, ongoing updates, and data reconciliation.
• State-level interfaces where labour code rules interplay with central execution. For context on uneven state readiness, see states delaying labour code rules and steps to manage risk and a state example in Gujarat’s Labour Code Rules checklist.

HR and payroll steps to prepare this quarter

1. Identify if you are an aggregator or a hirer on a third-party platform. If you operate a marketplace or delivery app that allocates work, assume you are an aggregator. If you only hire through someone else’s platform, your primary role is data-sharing and contract hygiene, not contribution remittance.
2. Create a gig worker master. Capture full name, mobile, government ID where lawful, bank or payout handle, category of service, cities of operation, and engagement dates. Treat it like an employee master for compliance integrity.
3. Clean your KYC data. Validate duplicates across multiple emails or numbers. Standardize names to reduce future rejection during central registration.
4. Refresh agreements. Add clauses that allow you to register workers for social security, explain data usage, and outline how contributions will be handled when rules are notified. Keep language consistent across aggregator, vendor, and worker terms.
5. Update payout systems. Tag every transaction to a worker ID and service category. This will later drive contribution computations and audits. If you run complex payroll and payouts, align with your payroll processing steps and month-end close.
6. Set up a contribution accrual ledger. Even before exact rates are notified, create a provisional account to accrue expected obligations. This avoids a year-end shock when contributions are finalized.
7. Build an audit trail. Keep logs of task acceptance, completion, and payout timestamps. Retain communication records that show the nature of the engagement. You will need this to prove eligibility and coverage.
8. Plan worker communication. Draft simple FAQs explaining what social security coverage means, what will change in onboarding, and how workers can update their details.
9. Nominate a compliance owner. Assign one person to track central notifications and state rule interplay. Use trusted trackers such as state rule notification updates to avoid surprises.
10. Run a pilot registration dry run. Even if APIs are pending, simulate the flow with CSVs. Check how many records have missing fields, and fix data quality now.

Edge cases to watch

Workers active on multiple platforms

A driver may accept trips on more than one app the same day. You will likely contribute only for activity on your platform, while other platforms contribute for theirs. Prevent double-counting by reconciling to your own payout ledger and the worker’s unique registration ID once available.

Aggregators using third-party fleet or vendor partners

If you allocate work through your app but the rider is on a fleet partner’s rolls, you may still be the aggregator for social security purposes. Structure your vendor agreements to ensure data flow, registration consent, and clarity on who remits.

Mixed workforce companies

Many SMBs employ a core team plus gig workforce for peaks. Keep employee PF and ESIC fully separate from gig social security. For employees, normal EPF rules including the current wage ceiling apply. For a refresher on that change in 2026, see the EPF wage cap update. For ESIC, revisit how ESIC benefits work for employees so you do not mix frameworks.

Comparison: employees vs gig workers under social security

Area	Employees on payroll	Gig or platform workers
Legal basis	Existing PF, ESIC and related employee laws	Code on Social Security, 2020 provisions for gig and platform workers
Relationship	Employer-employee	Commercial engagement without employment
Who contributes	Employer and sometimes employee	Aggregator or platform as notified for covered workers
Registration ID	PF, ESIC numbers as applicable	Gig worker registration on the designated central system
Benefit delivery	Statutory PF, pension, medical as per law	Specific schemes to be notified for gig and platform categories
Compliance cycle	Monthly remittances with returns	To be detailed in scheme rules and aggregator instructions
Key risk	Delayed remittance, calculation errors	Misclassification, missing registration, under-contribution

Record keeping and data you will need

Expect registration to require accurate identity and engagement information. Prepare the following fields now so you can upload quickly once the portal workflow is live:

• Full name as per ID, date of birth, and contact details
• Bank or payout account, UPI or wallet handle as used for payouts
• Service category and city of operation
• Date of first engagement on your platform and current status
• Unique internal worker ID linked to every payout
• Consent records for data processing and social security registration

Keep these synchronized across your CRM, payout system, and HR records. Your reconciliation effort will be far lower at month end if your IDs match across systems.

Compliance risks if you wait

Financial exposure. If you do not accrue and the contribution becomes payable with retrospective effect, you may face a large unplanned outflow along with interest or penalties.

Operational disruption. Platform-level registration could become a go-live blocker if you cannot supply clean worker data on short notice.

Reputational and legal risk. Misclassification or non-registration disputes are costly and public. Courts and regulators generally look at substance over labels.

How this affects monthly close and payroll operations

Even if the contribution is not part of employee payroll, treat it as a statutory charge tied to payouts. Build it into your month-end rhythm just like PF or ESIC for employees.

• Create a provisional calculator tied to your gig payout ledger.
• Post a monthly accrual entry to a dedicated liability account.
• Track reversals once the exact scheme rates and payment window are notified.
• Document your assumptions and approvals for audit readiness.

If you already manage a structured close, adapt it using the same discipline you apply to payroll processing in India.

Watchlist and next milestones

Monitor three things closely in 2026:

• The scheme notification that defines benefits and the collection mechanism for aggregators.
• The registration portal workflow and bulk upload formats.
• Any state-level notifications that add procedural layers for platforms operating in those states, similar to how some states progressed earlier on labour code rules such as Gujarat, while others delayed as covered in this state delay explainer.

Real-world scenarios

Food delivery aggregator in Bengaluru. You run a delivery app with 4,500 active riders in a month. Start cleaning KYC, tag every order to a rider ID, and set up a contribution accrual linked to monthly payouts. Update your fleet partner contracts to clarify data sharing and registration consent.

SaaS startup using on-demand testers. You do not operate a marketplace. You hire testers through a third-party platform. Your role is to ensure your vendor contract requires the platform to comply with gig social security and to provide you worker registration confirmation for your records.

Logistics company with employees and gig workers. Your warehouse staff are employees with PF and ESIC. Your last-mile riders accept routes through your app. Keep two separate compliance tracks. Use your employee PF learnings to structure monthly reconciliations but do not mix the frameworks.

Bottom line and next actions

The big change is simple: the law now expects platforms to provide a social security floor for gig workers. The details will arrive, but you cannot wait to fix data, contracts, and systems.

• Decide if you are an aggregator and document your reasoning.
• Build a clean gig worker master and start monthly payout reconciliations.
• Refresh contracts to cover registration, data usage, and contributions.
• Stand up a contribution accrual and a basic calculator for internal tracking.
• Assign ownership to track notifications and be ready to implement fast.

If you act on these items now, you will switch on compliance with minimal disruption when the rules and portals go live.

Related reading

• Awareness Programme on Labour Codes in New Delhi
• Biometric vs Mobile Attendance for Manufacturing Workers
• Salary pay slip online: download, verify, fix issues
• Supreme Court ruling on gratuity liability: what HR must do