Employer correction
Correct master data, contribution/return or evidence through the authorised route while retaining the original record and reason.
Regulation 95E: Submission of claim for funeral expenses
Regulation-wise current-law crosswalk, implementation controls, evidence, remedies and transition treatment.
Current legal status and scope
Regulation 95E governs benefit-claim validity or processing: Submission of claim for funeral expenses.
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 benefit type, insured status, qualifying contribution condition and event date.
Identify the benefit type, insured status, qualifying contribution condition and event date.
Implementation test: fix the event date, responsible person, evidence source, current Code/Rule owner and any later ESIC instruction before concluding compliance.
Control 2: Use the current claim channel and preserve medical/employment evidence and claimant identity.
Use the current claim channel and preserve medical/employment evidence and claimant identity.
Implementation test: fix the event date, responsible person, evidence source, current Code/Rule owner and any later ESIC instruction before concluding compliance.
Control 3: Issue a deficiency request rather than rejecting solely for a curable form defect where law permits.
Issue a deficiency request rather than rejecting solely for a curable form defect where law permits.
Implementation test: fix the event date, responsible person, evidence source, current Code/Rule owner and any later ESIC instruction before concluding compliance.
Control 4: Record the due date, approval, payment date, withholding reason and review/appeal path.
Record the due date, approval, payment date, withholding reason and review/appeal path.
Implementation test: fix the event date, responsible person, evidence source, current Code/Rule owner and any later ESIC instruction before concluding compliance.
Control 5: Funeral-expense claims require death and expenditure/claimant-status evidence; use the current benefit limit under Rule 21 and current ESIC claim route.
Funeral-expense claims require death and expenditure/claimant-status evidence; use the current benefit limit under Rule 21 and current ESIC claim route.
Implementation test: fix the event date, responsible person, evidence source, current Code/Rule owner and any later ESIC instruction before concluding compliance.
Responsible parties
Insured person or dependant, employer, Insurance Medical Officer and ESIC branch/benefit authority
Trigger
Sickness, maternity, employment injury, death or another insured contingency gives rise to a claim.
Current-law crosswalk
Primary Code sections: 32, 38, 39, 40. Central Rules: 21, 22, 25, 26.
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
- insured-person record
- claim and acknowledgement
- medical certificate or death evidence
- wage/abstention confirmation
- decision and payment record
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
Missing evidence or late submission may delay, reduce or suspend benefit, subject to cure, relaxation and appeal rights.
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 95E — Submission of claim for funeral expenses. 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 95E 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.
Related provisions and tools
Code section 32Current Code provisionCode section 38Current Code provisionCode section 39Current Code provisionCode section 40Current Code provisionCentral Rule 21Social Security (Central) Rules, 2026Central Rule 22Social Security (Central) Rules, 2026Central Rule 25Social Security (Central) Rules, 2026Central Rule 26Social Security (Central) Rules, 2026ESI concordanceCode–Rule–Regulation map2026 Regulations statusDraft/replacement watch