Finin2min · Finance & Law Explained in 2 Minutes
Legal position as at 9 July 2026

Gig, Platform and Unorganised Workers Hub

Registration, social security schemes, aggregator obligations, funding, records and implementation readiness.

In 2 minutes

1

The Code recognises unorganised, gig and platform workers.

2

Benefits depend on notified schemes, eligibility and registration.

3

Aggregators need category and turnover/contribution data readiness.

4

Worker identity and portability are central operational issues.

5

The National/State Boards and scheme rules drive implementation.

6

Public pages must distinguish enacted framework from a benefit actually operational for a worker.

Legal map

  • Social Security Code Chapter IX
  • Social Security (Central) Rules, 2026 rules 48–50
  • Notified schemes and aggregator instruments
  • State implementation

Owner actions

  1. Map business model to aggregator categories.
  2. Maintain worker/transaction data capable of scheme reporting.
  3. Track notified contribution and scheme rules.
  4. Support worker registration and grievance channels.

Practical examples

ScenarioFinin2min treatment
Employee worked 240 days but wage exceeds the notified eligibility ceilingDo not use the historic ceiling automatically. Test the current notification under section 26 before concluding eligibility.
Company has allocable surplus and an earlier set-on balancePrepare the four-year set-on/set-off schedule before fixing the payable percentage.
Employee’s basic+DA is above the mandatory ceiling at joiningTest excluded-employee status, prior membership and the EPF Scheme 2026; do not decide from salary alone.

Common control failures

Using historic thresholds without the operative notification; ignoring state rules; relying on CTC labels; accepting aggregate contractor challans; missing effective dates; and publishing a calculation without assumptions or source status.

Questions and answers

Is this Gig, Platform and Unorganised Workers Hub a substitute for the official law?

No. It is an explanation and control layer. The official Code, rules, scheme, notification, state instrument and case law govern.

What date is the legal position based on?

The central legal position was reviewed as at 9 July 2026. State instruments and portals should be checked on the transaction date.

Why are legacy Acts still shown?

They help users understand subject history, savings, past periods, pending proceedings and transition into the Codes.

Which government is the appropriate government?

It depends on the establishment and statutory definition. Central-sector establishments generally fall to the Central Government; others generally fall to the State Government, subject to the exact provision.

What evidence should an employer retain?

Applicability memo, employee/worker master, attendance, wage sheets, bank proof, challans, returns, notices, approvals, acknowledgements and exception closure.

Can a calculator decide legal eligibility automatically?

Only when every legal input and current notification is available. Otherwise it should show an unresolved input rather than a confident number.

How should contractor compliance be checked?

Worker-wise by identity/UAN/IP number, attendance, wage, bank credit and statutory contribution—not only by aggregate challan.

What should be shown on a public article?

Official source, instrument status, effective date, state/central scope, last verification date, assumptions, examples and disclaimer.

How often should the hub be reviewed?

High-risk portals and notifications should be monitored frequently; the formal source register should be reviewed at least quarterly and on every material event.

Are state laws included?

The package includes a state-overlay structure. Exact state Acts, rules, rates, forms and portals must be populated and verified state by state.

Repository links

Source discipline: exact legal text and live state/portal position must be checked before publishing or acting.