Employer correction
Correct master data, contribution/return or evidence through the authorised route while retaining the original record and reason.
Regulation 32: Register of employees engaged by immediate employer
Regulation-wise current-law crosswalk, implementation controls, evidence, remedies and transition treatment.
Current legal status and scope
Regulation 32 governs the operational subject described as “Register of employees engaged by immediate employer” within the saved 1950 Regulations.
Transition control: The ESI Act, 1948 has been repealed. Code section 164(2)(b) keeps ESI rules, regulations and schemes in force for one year from commencement, only to the extent not inconsistent with the Code; section 164(2)(a) separately preserves prior actions subject to its conditions. The Corporation approved framing of 2026 General Regulations on 30 June 2026; this page does not treat that approval as a final Gazette replacement. Consolidated regulation text.
Regulation-specific legal and control map
Control 1: Identify the legal actor, statutory event and current Code provision before applying the legacy procedure.
Identify the legal actor, statutory event and current Code provision before applying the legacy procedure.
Implementation test: fix the event date, responsible person, evidence source, current Code/Rule owner and any later ESIC instruction before concluding compliance.
Control 2: Translate paper-era references into the current ESIC portal/office workflow without deleting mandatory evidence.
Translate paper-era references into the current ESIC portal/office workflow without deleting mandatory evidence.
Implementation test: fix the event date, responsible person, evidence source, current Code/Rule owner and any later ESIC instruction before concluding compliance.
Control 3: Retain the original event record, maker-checker review and acknowledgement or reasoned decision.
Retain the original event record, maker-checker review and acknowledgement or reasoned decision.
Implementation test: fix the event date, responsible person, evidence source, current Code/Rule owner and any later ESIC instruction before concluding compliance.
Control 4: Check later ESIC directions and the pending 2026 regulation replacement before each material use.
Check later ESIC directions and the pending 2026 regulation replacement before each material use.
Implementation test: fix the event date, responsible person, evidence source, current Code/Rule owner and any later ESIC instruction before concluding compliance.
Responsible parties
Employer, insured person, ESIC authority or medical authority according to the transaction
Trigger
The facts engage register of employees engaged by immediate employer.
Current-law crosswalk
Primary Code sections: 31, 121. Central Rules: 53.
Do not duplicate: the full Code and Central Rule analysis remains under the L3 Social Security corpus. This page owns only the saved regulation and its operational transition.
Evidence and audit trail
- source transaction record
- coverage/identity evidence
- prescribed communication
- approval or decision
- audit trail
Quality controls
- Event date and legal-version lock.
- Employee/insured-person identifier reconciliation.
- Maker-checker review and exception log.
- Current portal acknowledgement or reasoned authority decision.
- Privacy-controlled retention of medical and dependant records.
Non-compliance, remedy and escalation
Incorrect application may affect contribution liability, benefit entitlement, recovery or appeal.
Insured person or claimant
Use the appropriate claim, grievance, Medical Board, review, ESI Court or High Court route according to the disputed issue.
Authority control
Keep assessment, benefit, interest, damages, recovery and penalty decisions separately reasoned and quantified.
Worked implementation scenario
A transaction arises under Regulation 32 — Register of employees engaged by immediate employer. The compliance owner records the event date and identifies whether the issue concerns coverage, contribution, medical evidence or benefit. The current Code section and 2026 Central Rule are checked first; the saved regulation is then used only for the surviving operational detail. The maker prepares the portal filing, claim or decision pack, while a reviewer verifies identity, wage/contribution or medical evidence, limitation and later ESIC directions. The acknowledgement, calculation and correspondence are preserved together.
Failure pattern: copying the paper-era process without checking whether the Code, final Central Rules or ESIC digital workflow has displaced it.
Practical Q&A
Is Regulation 32 automatically current because it appears in a consolidated text?
No. It survives only through the Code’s savings framework and only to the extent it is not inconsistent with the Code, final Central Rules or a later valid replacement.
Can portal acceptance cure an incorrect legal classification?
No. Portal processing does not conclusively determine coverage, contribution wage, medical entitlement, dependant status or limitation.
Should the proposed 2026 General Regulations be used now?
Not as final law unless and until a valid Gazette notification brings the replacement instrument into force. Track the official status page.