Reference: ESIC Headquarters communication F.No. P-14011/2/2026-BFT-II dated 4 August 2026, addressed to all Regional Directors / Joint Directors (I/c), issued with the approval of the Insurance Commissioner and signed by the Deputy Director (Benefit). A User Manual is enclosed with the circular.
1. What has been notified
ESIC has developed a new Insured Person (IP) Registration functionality within its ERP system for registering employees under the Employees’ State Insurance Scheme. In ESIC’s own description, the module is designed to enable seamless registration of Insured Persons, capture of the requisite particulars, and generation of the Insurance Number.
Two points in the circular deserve the attention of every covered employer. First, ESIC states that the module shall be used by the employer for processing and facilitating registration-related activities — registration remains an employer obligation, now routed through a new interface. Second, employees may themselves complete the authentication step through the ESIC Health Connect App, which ESIC describes as making the process simpler and more user-friendly.
2. The circular at a glance
Particulars | Position |
Issued by | ESIC Headquarters, Panchdeep Bhawan, New Delhi — Deputy Director (Benefit) |
File / Date | F.No. P-14011/2/2026-BFT-II | 4 August 2026 |
Addressed to | All Regional Directors / Joint Directors (I/c); copies to Insurance Commissioner (ICT), Web Content Manager, all Branch Offices |
Subject | Implementation of the new Insured Person (IP) Registration functionality in ERP |
Who operates it | The employer — for processing and facilitating registration-related activities |
Employee’s role | Employees may complete the authentication process themselves via the ESIC Health Connect App |
Output | Capture of requisite details and generation of the Insurance Number |
Documentation | User Manual with workflow, operating instructions, screenshots and step-by-step guidance, enclosed with the circular |
Field action | ROs/SROs to circulate the User Manual, run orientation and training for field functionaries, and assist employers and IPs in using the new process |
Website | The Web Content Manager has been asked to upload the User Manual and related instructions on the ESIC website / portal |
3. Why this matters to you
Read on its own, this is an IT release note. Read alongside the direction of ESIC’s recent digitisation — and the draft ESI (General) Regulations, 2026 currently in circulation — it signals a shift in where the burden of getting registration right actually sits.
▪ Onboarding data quality becomes the critical control. An app-based authentication step by the employee only works if the mobile number captured at onboarding is the one linked to the employee’s Aadhaar. Mismatches will surface as failed or pending registrations rather than as a quiet back-office correction.
▪ Registration is no longer purely an HR back-office task. If the employee has to act — install an app, authenticate — then HR must communicate, follow up and track completion. Build that follow-up into the joining checklist rather than assuming it will happen.
▪ The statutory clock has not changed. The obligation to register a newly covered employee within ten days under the ESI (General) Regulations, 1950 stands exactly where it was. A new interface is not an extension of time, and “the employee had not completed app authentication” is unlikely to survive as a defence in an inspection.
▪ Delayed registration is a benefit problem before it is a compliance problem. An employee without an Insurance Number cannot draw sickness, maternity or, critically, employment injury benefit. In an accident case, a registration gap turns into a Section 68 recovery exposure against the employer.
4. Suggested action points
Action | Detail |
Brief the payroll / HR operations team | Ensure whoever handles ESIC registration is aware that a new ERP module now governs the process, and that the old habits of the earlier flow may not carry over. |
Fix onboarding data capture | Collect the Aadhaar-linked mobile number at the point of joining and validate it. This single field will determine whether app-based authentication succeeds. |
Add the Health Connect App to the joining kit | Tell new joiners, in the appointment or joining communication, that they may be required to authenticate through the ESIC Health Connect App, and by when. |
Track pending registrations weekly | Maintain a simple joiner-to-IP-number tracker with ageing. Anything crossing ten days should escalate, not sit in a queue. |
Preserve evidence | Retain the registration acknowledgement and Insurance Number allotment for every joiner. This is the first document an inspecting officer asks for. |
Watch for the User Manual | ESIC has directed that the manual be uploaded on its website. Download it when it appears and align your internal SOP to the documented workflow. |
5. Points on which the circular is silent
We flag these deliberately, so that you plan around them rather than assume:
▪ The circular does not specify a go-live or cut-over date for the new module.
▪ It does not state whether the existing registration route on the employer portal stands withdrawn or will run in parallel for a transition period.
▪ It does not clarify whether authentication through the ESIC Health Connect App is mandatory or an optional convenience — the wording (“may complete”) suggests the latter, but the operational reality will be settled by the User Manual.
▪ It does not address the treatment of employees without a functioning Aadhaar-linked mobile number, which in practice is the largest category of registration failures at the shop-floor level.