Skip to main contentSkip to contentSkip to content
Labour portal operating guide

Shram Suvidha and Labour Identification Number

Reviewed by Ravi Sisodia · Last reviewed 28 July 2026

Registration, inspection and compliance services; the legacy portal now directs new Labour Code activity to the new portal while retaining historical records.

Ministry of Labour and EmploymentReviewed 2026-07-28Official portal links
Portal in 2 minutes

Registration, inspection and compliance services; the legacy portal now directs new Labour Code activity to the new portal while retaining historical records.

Law-versus-system boundary: Portal acceptance records a filing; it does not determine legal coverage, exemption or substantive compliance.
Legacy-route notice

The official login states that the new Labour Code Portal is live and that the older portal continues for historical records. Choose the route shown by the Ministry on the transaction date.

Check the official operating notice ↗

Before you log in

Finin2min filing workflow

1
Confirm the legal route.
Identify the establishment, worker, appropriate Government, applicable law and due date.
2
Reconcile master data.
Match identity, registration, wage, contribution and authorised-signatory records before filing.
3
Submit and preserve evidence.
Save the acknowledgement, payload, attachments, challan, payment proof and timestamp.
4
Track exceptions.
Record error messages, ticket numbers, grievance or appeal routes and statutory limitation separately.

Evidence file

RecordWhy retain it
Pre-filing reconciliationShows the basis for identity, wage, contribution and legal classification.
Submitted payload and attachmentsProves what information was actually filed.
Acknowledgement and payment trailSupports filing date and payment status.
Portal error and grievance trailSeparates technical delay from legal non-compliance.
Final order or communicationPortal status alone may not be the operative legal decision.
Official access

Open the principal official portal ↗
Open the connected official resource ↗

Portal interfaces and availability can change. Confirm notices displayed by the owning authority on the filing date.

Finin2min Q&A

Does a successful upload prove legal compliance?

No. It proves system submission. Coverage, classification, due date, evidence and substantive entitlement remain governed by law.

What should be done during an outage?

Preserve timestamped screenshots, error text and helpdesk tickets; use any authorised alternate route and separately protect statutory limitation.

Source and review trail

Use the current official instrument, portal or regulator publication before acting.

Official starting point
www.labour.gov.in

Legacy and current portal routing

Choose the portal from the legal transaction and the Ministry's live notice. The legacy Shram Suvidha environment may retain earlier registrations, LIN, inspections and return history while Labour Code functions move to a current portal. Preserve both histories where the establishment crosses the transition.
TaskPre-filing controlEvidence after submission
LIN or establishment profileReconcile PAN/CIN, legal name, address, units, authorised signatory and existing labour registrations.Profile version, change request, approval and old-to-new identifier map.
Registration or licenceIdentify appropriate Government, establishment/activity, worker thresholds, contractor/principal employer and State interface.Application payload, attachments, fee, certificate and conditions.
Return or contribution dataBridge payroll, attendance, wages, contractor data and law-specific registers to the portal fields.Filed payload, acknowledgement, challan and exception reconciliation.
InspectionVerify inspector authority, inspection scheme, establishment and requested period.Notice, documents supplied, inspection report, response and closure/order.

Transition workflow

  1. Inventory records
    Export legacy identifiers, certificates, filings and pending actions.
  2. Read live notice
    Record the Ministry instruction displayed for the transaction date.
  3. Map migration
    Reconcile users, establishments, laws and open matters in the current portal.
  4. Prove continuity
    Keep both acknowledgements and helpdesk/escalation evidence where data does not migrate.

Outage example: If the current portal rejects an establishment mapping near a statutory deadline, capture the complete error, payload and timestamp, raise the official ticket and use only an authorised alternate route. A screenshot supports the technical chronology; it does not automatically extend limitation or prove substantive compliance.

Official access

Shram Suvidha dashboard | legacy login | Ministry Labour Codes resource

Portal ownership, routes and schemas can change. Follow the live Ministry notice and the law applicable to the establishment, State and filing period.