Employer correction
Correct master data, contribution/return or evidence through the authorised route while retaining the original record and reason.
Regulation 109: Submission of additional information by employer or insured person
Regulation-wise current-law crosswalk, implementation controls, evidence, remedies and transition treatment.
Current legal status and scope
Regulation 109 supports inspection, verification or continuing disclosure: Submission of additional information by employer or insured person.
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: Maintain retrievable payroll, contractor, contribution, claim and medical-entitlement evidence.
Maintain retrievable payroll, contractor, contribution, claim and medical-entitlement evidence.
Implementation test: fix the event date, responsible person, evidence source, current Code/Rule owner and any later ESIC instruction before concluding compliance.
Control 2: Respond within the authorised request and preserve exactly what was supplied.
Respond within the authorised request and preserve exactly what was supplied.
Implementation test: fix the event date, responsible person, evidence source, current Code/Rule owner and any later ESIC instruction before concluding compliance.
Control 3: Keep an immutable inspection/action log with owner, due date, response and closure evidence.
Keep an immutable inspection/action log with owner, due date, response and closure evidence.
Implementation test: fix the event date, responsible person, evidence source, current Code/Rule owner and any later ESIC instruction before concluding compliance.
Control 4: Escalate privilege, personal-data and medical-confidentiality issues without obstructing lawful inspection.
Escalate privilege, personal-data and medical-confidentiality issues without obstructing lawful inspection.
Implementation test: fix the event date, responsible person, evidence source, current Code/Rule owner and any later ESIC instruction before concluding compliance.
Responsible parties
Principal employer, immediate employer, insured person, Social Security Officer and authorised ESIC officer
Trigger
Inspection, information request, document production requirement or change in benefit circumstances.
Current-law crosswalk
Primary Code sections: 121, 122, 123, 124. 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
- inspection request/order
- records index
- response pack
- inspection book/action tracker
- remediation evidence
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
Non-production or inaccurate information may support assessment, penalty, benefit action or prosecution.
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 109 — Submission of additional information by employer or insured person. 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 109 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.