Gig and platform worker social security contributions are now a live compliance question for any Indian subsidiary that engages delivery partners, drivers, field agents, or on-demand specialists as contractors. Foreign parent companies, NRI founders, global startups, and overseas investors often assume that a contractor label ends the obligation. Under India’s labour code reforms, that assumption can be costly. Whether your subsidiary owes a levy, must support worker registration, or faces misclassification risk depends on how it uses technology, how it controls work, and what it pays. This guide explains the framework in plain terms, so decision-makers can act before a notice arrives. Startup Solicitors LLP regularly advises foreign-owned entities on exactly these structuring questions.
Understanding Gig and Platform Worker Social Security in the Indian Context
India’s Code on Social Security, 2020 was the first Indian statute to formally recognise gig workers and platform workers. The Union government brought the four labour codes into force on 21 November 2025, so the framework now sits inside active compliance planning.
- Gig worker: a person who earns from work outside a traditional employer-employee relationship.
- Platform worker: a gig worker whose work is arranged through an online platform.
- Aggregator: a digital intermediary or marketplace that connects a buyer or user with a service provider. The Code’s schedule lists categories such as ride sharing, food and grocery delivery, logistics, e-marketplaces, professional services, healthcare, travel and hospitality, and content and media.
The key point for foreign groups is that the obligation attaches to the aggregator role, not to the word “contractor.” A subsidiary that merely hires an independent consultant is not automatically an aggregator. A subsidiary that runs an app matching customers with workers likely is. The two paths carry very different compliance outcomes.
Legal Framework and Regulations in India
The main sources are the Code on Social Security, 2020, central and state rules framed under it, and the e-Shram portal run by the Ministry of Labour and Employment. Corporate and tax angles are governed by the Companies Act, 2013 (see MCA) and the Income-tax Act (see the Income Tax Department).
| Element | Position under the Code |
|---|---|
| Who contributes | Aggregators |
| Contribution rate | 1% to 2% of annual turnover, capped at 5% of amounts paid or payable to gig and platform workers |
| Fund | Social Security Fund for gig and platform workers |
| Worker registration | Through e-Shram, linked to Aadhaar |
| Benefits | Life and disability cover, health, maternity, old-age protection, as notified in schemes |
The exact rate within the 1% to 2% band, eligibility thresholds, and reporting formats are set through notifications and rules. Draft central rules proposed engagement-day thresholds for worker eligibility. Confirm the current notified position before filing anything.
Foreign-owned subsidiaries must also respect FDI and reporting rules, so align labour planning with FEMA and RBI compliance.
Step-by-Step Process Explained
- Map every contractor relationship. List who is engaged, how they are paid, who sets schedules, and whether work flows through your app or portal.
- Test your aggregator status. Check whether your digital platform matches a Schedule category and whether you connect users with service providers.
- Test for misclassification. Control over hours, tools, exclusivity, and training points towards employment, which triggers EPF, ESIC, and gratuity rules instead.
- Compute the contribution. Apply the notified percentage to annual turnover and compare against the 5% payout cap. The lower figure governs.
- Support registration. Collect worker details and guide onboarding on e-Shram.
- Record and report. Maintain payment ledgers, contract files, and board-level compliance notes.
- Review yearly. Revisit the model when turnover, product features, or worker volumes change.
Considerations by stakeholder:
- Indian residents: Founders running a platform business should build the levy into pricing and unit economics from day one.
- NRIs: Remote directors should confirm that board minutes record the classification decision.
- Foreign companies: Parent-level contractor agreements must not override Indian status tests. Coordinate with payroll management teams early.
- Global startups: Entering India through a marketplace model usually brings aggregator status. Plan this during company setup in India.
- Overseas investors: Add gig-labour exposure to due diligence checklists, supported by corporate governance compliance reviews.
Key Challenges and Practical Issues
Common mistakes
- Treating every contractor as outside the Code.
- Copying a foreign parent’s contractor template without Indian review.
Compliance risks
- Retrospective demands where a worker is later found to be an employee.
- Mismatch between turnover figures in GST returns and the levy base.
Documentation issues
- Missing service agreements, unclear payment trails, and absent worker identity records.
Regulatory hurdles
- State-level gig worker laws, such as Rajasthan’s and Karnataka’s, add parallel duties. Rules are evolving, and notifications differ across states.
Practical challenges
- Workers often serve several platforms, making attribution of engagement days difficult.
- Finance teams need clean turnover data, so outsourced accounting services can help.
Tax alignment matters as well. Payments to contractors raise TDS questions, and your taxation and compliance services partner should reconcile them.
Strategic Insights and Expert Recommendations
- Decide your model before launch. During company formation in India, choose between a marketplace, a staffing partner, or direct hiring. Each carries a distinct contribution profile. A properly structured private limited company is the usual vehicle.
- Build a classification matrix. Score each role on control, exclusivity, tools, and tenure. Roles scoring high on control should move to employment.
- Budget the levy as a cost of revenue. A turnover-linked charge affects gross margin, so model it at both the 1% and 2% ends.
- Keep the parent at arm’s length. Intercompany charges for platform services should be supported by transfer pricing compliance.
- Prepare for GST interplay. Platform operators often face supply-side GST duties; confirm GST registration scope.
- Use sector expertise. Mobility and delivery models carry special risks; review fleet management and ride-sharing compliance or logistics and supply chain guidance for your vertical.
For a structured review, corporate law and legal advisory support can convert these points into a written policy, and a business setup in India for foreign nationals specialist can align it with your parent’s global structure.
FAQs
1. Do Indian subsidiaries have to pay gig and platform worker social security contributions?
Only if the subsidiary qualifies as an aggregator under the Code on Social Security, 2020. A company that merely hires independent contractors is generally outside this levy, but may face employment-law exposure if the contractors are misclassified.
2. What is the contribution rate for aggregators?
The Code sets aggregator contributions at 1% to 2% of annual turnover, capped at 5% of amounts paid or payable to gig and platform workers. The exact rate is notified by the government, so check the latest notification before budgeting.
3. How do workers register for benefits?
Gig and platform workers register on the government’s e-Shram portal using Aadhaar-linked details. Aggregators are expected to share worker information and support onboarding so that benefits under notified schemes reach eligible workers.
4. Can a foreign parent company be treated as an aggregator?
Aggregator status depends on activity in India. If a foreign parent operates a platform serving Indian users through a local entity, the Indian subsidiary typically carries compliance responsibility. Cross-border structures should be reviewed individually with qualified Indian counsel.
5. What happens if contractors are reclassified as employees?
The company may owe EPF, ESIC, gratuity, and other statutory dues with possible interest and penalties. Clear contracts, genuine operational independence, and periodic classification audits are the best protection against retrospective claims.