ESIC Mobile Number Bank Details Mandatory From 01-07-2020

ESIC Mobile Number Bank Details Mandatory is an important historical ESIC compliance update introduced with effect from 1 July 2020. The Employees’ State Insurance Corporation issued circular F. No. I-11/13/04/2020-ICT dated 29 June 2020 and directed that mobile number and bank-account details of an employee would become a mandatory prerequisite for registering the person as an Insured Person. ESIC stated that the objective was to improve the efficiency of benefit disbursement, including claim reimbursement, and to bring greater transparency into the process.

The ESIC Mobile Number Bank Details Mandatory requirement changed the employee registration workflow on the ESIC employer portal. Employers had to provide correct mobile information for the employee and bank-account information for the beneficiary. The ESIC system introduced validation controls to reduce incorrect or junk data, while special validation through OTP was available in situations involving duplicate or ambiguous mobile-number entries.

This historical ESIC update is useful for employers, HR departments, payroll teams, compliance professionals and businesses reviewing registration records from July 2020 onward. It is also useful when checking why an employee’s ESIC registration required mobile and bank details or why certain records needed correction through the employer portal.

What Is ESIC Mobile Number Bank Details Mandatory?

ESIC Mobile Number Bank Details Mandatory refers to the ESIC requirement that correct mobile and bank details be provided as part of the registration or enrolment process for an Insured Person with effect from 1 July 2020.

The circular was issued on 29 June 2020 and specified implementation from 1 July 2020. The requirement applied to the registration of new Insured Persons and also provided processes for updating information for existing Insured Persons.

For mobile numbers, the employer had to enter the employee’s correct mobile number and use the system’s validation process. For bank details, the employer had to enter the relevant IFSC and employee account number, with the system checking the information and preventing certain duplicate or invalid entries.

The requirement was designed to make benefit payments and claim reimbursements more efficient and transparent and to improve the reliability of beneficiary information.

ESIC Mobile Number Mandatory From 01-07-2020

ESIC Mobile Number Mandatory became effective from 1 July 2020. The employer registration process required the correct mobile number of the employee being registered or enrolled to be entered before proceeding further.

ESIC’s official manual explains that this mobile number had to be captured at the first stage of registration. Once the mobile number was entered and auto-validated by the system, the employer could proceed to the remaining registration fields.

The manual specifically cautioned employers to enter the beneficiary’s correct mobile number from the beginning because the number entered at the start of the process remained fixed throughout the registration workflow.

This made accuracy particularly important. An incorrect number could create communication difficulties and could require later correction through the appropriate ESIC employer-portal workflow.

Why Mobile Number Was Made Mandatory

The ESIC circular stated that the requirement was introduced to improve efficiency in disbursement of ESIC benefits and claim reimbursements and to bring transparency.

A valid mobile number can support communication and validation in an electronic service environment. ESIC therefore incorporated validation into the registration process instead of allowing unrestricted entry of unverified numbers.

For employers, this meant that employee information had to be collected carefully before registration. Incorrect or incomplete information could lead to errors and additional administrative work.

For compliance teams, the change also reinforced the importance of maintaining accurate employee records and updating outdated information.

Mobile Number Validation In ESIC Portal

The ESIC Mobile Number Mandatory process included automatic validation. When an employer entered a mobile number, the system checked whether the number was already associated with an Insured Person.

If the number was unique and acceptable, the registration process could continue. If the number was already associated with another Insured Person, the system displayed an alert.

In a duplicate situation, the employer was expected to enter a different correct mobile number. The official manual also described an exception where the employer could certify that the mobile number actually belonged to the employee or spouse and proceed through the additional validation process.

This was an important control because it attempted to reduce duplicate or incorrect mobile-number entries in the ESIC database.

OTP Verification For Duplicate Mobile Numbers

One of the most useful parts of the ESIC Mobile Number Bank Details Mandatory workflow was the OTP mechanism.

Where a mobile number was already tagged with an Insured Person or Insured Woman and the employer still certified that the number was correct for the current employee, an OTP could be generated for validation.

The ESIC manual states that the employee received the OTP through SMS and that the employer had to enter the OTP and verify it before proceeding.

The manual also included an important control: the employer could generate a maximum of three consecutive OTPs at one time, after which the system would restrict further OTP generation for three hours.

This validation mechanism was designed to improve data quality and reduce the risk of incorrect mobile-number seeding.

ESIC Bank Details Mandatory From July 2020

ESIC Bank Details Mandatory became part of the same registration and enrolment workflow from 1 July 2020.

The employer had to provide the correct bank credentials of the employee or Insured Person. The ESIC manual specifies that capturing the IFSC number was the first step in the bank-account process.

After the IFSC was entered and validated, the system could populate information such as bank name and branch. The employer then had to enter the employee’s account number.

This process was designed to make bank information more structured and to reduce incorrect or duplicate bank-account information.

IFSC Code In ESIC Registration

Under the ESIC Bank Details Mandatory process, the employer first entered the IFSC number.

The ESIC system then validated the IFSC and used it to retrieve bank-related information. This reduced the need for employers to manually enter every bank field and helped standardise the information captured in the ESIC database.

The IFSC step was therefore an important part of the bank-account registration process. Employers should enter the correct IFSC associated with the beneficiary’s account.

Using an incorrect IFSC could cause the bank information to be captured inaccurately and may require subsequent correction.

Bank Account Number And Account Type

After entering and validating the IFSC, the employer had to provide the employee’s bank-account number. The ESIC manual also shows selection of the account type and upload of supporting bank documentation.

The bank-account number had to be correct because the purpose of the process was to support accurate beneficiary information and efficient benefit-related transactions.

Employers were therefore advised to exercise caution when entering the account number. The ESIC manual states that the employer would be responsible for consequences arising from incorrect information being seeded into the system.

Upload Of Bank Documentary Evidence

Another important part of the ESIC Bank Details Mandatory process was documentary evidence.

The official ESIC implementation manual states that an attested copy of the bank passbook or cheque leaflet had to be scanned and uploaded as documentary evidence when capturing the bank credentials of a new employee.

This requirement provided an additional verification layer and helped support the accuracy of the information entered into the system.

For historical compliance records, businesses should therefore distinguish between the account number entered into the ESIC portal and the document used to support that entry.

ESIC Registration 01-07-2020

ESIC Registration 01-07-2020 refers to the employee registration and enrolment process that incorporated mandatory mobile and bank details from 1 July 2020.

The ESIC manual was created on 1 July 2020 and contains a detailed step-by-step workflow for registration of a new employee, enrolment of an employee who already had an Insurance Number, seeding of a mobile number, seeding of a bank account number and updating existing Insured Person details.

This makes the manual an important historical document for understanding how the employer portal operated when the new requirement was introduced.

Employers reviewing old ESIC registration questions can use the manual to understand the sequence in which the mobile and bank fields were captured.

Registration Of A New Insured Person

During ESIC Registration 01-07-2020, a new employee who had never previously held an ESI Insurance Number could be registered by the current employer to generate an Insurance Number.

Before continuing with the registration form, the employer had to enter the employee’s mobile number and validate it.

The registration process then included the bank-account details. The employer entered the IFSC, supplied the account number, selected the account type and uploaded supporting documentation before submitting the form.

This created a more structured registration process than the earlier workflow.

Enrolment Of An Employee With Existing IP Number

ESIC Registration 01-07-2020 also covered employees who already had an Insurance Number because of previous employment.

Such employees were enrolled by the current employer using the existing Insurance Number instead of creating a new number.

The ESIC manual provides separate procedures to update or seed the mobile number and bank details for an employee who already possessed an Insurance Number.

This supports the ESIC principle that one employee should continue with the same Insurance Number across employment relationships.

ESIC Insured Person Mobile Number

ESIC Insured Person Mobile Number became a significant employee-data field under the July 2020 process.

The official manual explains that the mobile number could be added or updated through the employer portal. Existing Insured Persons could have their mobile information corrected through the “Update Particulars of Insured Person” workflow.

Where the mobile number was unique, the system could enable the update directly after validation. Where it was already associated with another Insured Person, an alert and additional validation mechanism could apply.

This made the mobile number an important part of maintaining accurate Insured Person records.

Updating Existing Insured Person Mobile Details

The ESIC Mobile Number Mandatory requirement was not limited to newly created records. ESIC’s implementation manual also describes updating mobile numbers of existing Insured Persons.

An employer could access the update workflow, enter a mobile number and validate it. If the number was correct and unique, the update could proceed.

If the number was already tagged elsewhere, the employer was expected to enter a correct different number or use the specified certification and OTP mechanism where permitted.

This historical process demonstrates that ESIC placed importance on the quality of existing database records as well as new registrations.

Updating Existing Bank Details

The bank-account process similarly allowed updating the bank details of employees who already had an Insurance Number.

The employer could select the bank-detail update option, enter the IFSC, search for the bank information, enter the correct account number, select the account type and upload supporting documentation.

This was useful when employees changed bank accounts or when old records contained incomplete or incorrect information.

For historical audits, it can be helpful to distinguish between initial bank-account seeding and later bank-detail updates.

Importance Of Correct Employee Information

The ESIC Mobile Number Bank Details Mandatory requirement placed responsibility on employers to provide correct information.

The official manual repeatedly cautions employers about incorrect data. The mobile number entered during registration was expected to remain associated with the employee through the process, while incorrect bank information could also have consequences.

This means HR and payroll teams should have collected information from reliable employee documents before completing registration.

Correct information reduces administrative problems and supports smoother access to electronic ESIC services.

Why Accurate Bank Details Matter For Benefits

The original ESIC circular explained that the new requirement was introduced to improve the efficiency of disbursement of benefits, including claim reimbursements, and to bring transparency.

Correct beneficiary bank information is therefore important for benefit-related transactions where payment is made through the banking system.

An incorrect bank account can create delays, failed transactions or the need for correction. For that reason, the ESIC system introduced checks and documentary verification when bank details were seeded.

Common Mistakes In ESIC Mobile Registration

One common mistake was entering a mobile number without checking whether it actually belonged to the employee.

Another problem was using a number already associated with another Insured Person without following the additional validation process.

Employers could also encounter difficulties when an incorrect number was entered at the first step because the manual states that the number remained fixed through the registration process.

These issues show why employee information should be checked before registration instead of being entered hurriedly.

Common Mistakes In ESIC Bank Registration

For ESIC Bank Details Mandatory, common errors included entering an incorrect IFSC, entering the wrong account number or failing to provide the required documentary evidence.

A duplicate or incorrect account could also require correction before the information was accepted by the system.

Payroll and HR teams should therefore verify the employee’s bank document before entering the details into the ESIC portal.

Good recordkeeping reduces the risk of having to repeat the registration or update process.

Data Quality And Fraud Prevention

The ESIC circular and implementation manual show a clear emphasis on data validation. The mobile-number process included uniqueness checks and OTP authentication for specific duplicate situations.

The bank process used IFSC validation, account-number checks and documentary evidence. These controls were intended to improve data quality and prevent unreliable information from entering the database.

Accurate data also helps employers reduce administrative problems and supports proper delivery of statutory benefits.

Historical Compliance Importance

ESIC Mobile Number Bank Details Mandatory is particularly useful for businesses reviewing historical registrations made from July 2020.

If an old employee file shows that mobile or bank details were required at registration, the ESIC circular provides the background for that requirement.

Likewise, if an employer needs to understand the old portal workflow for correcting a mobile number or bank account, the official ESIC manual provides step-by-step documentation.

These records can be useful during audits, internal reviews and historical compliance verification.

Employer Responsibilities

Employers were responsible for entering correct employee information. The ESIC manual states that employers would be liable for consequences associated with incorrect information.

This made internal verification important. HR teams should have obtained the employee’s mobile and bank information carefully and retained supporting evidence where appropriate.

A practical compliance process includes verifying the employee’s name, Insurance Number where applicable, mobile number, IFSC, account number and bank document before completing registration.

ESIC Portal And Digital Compliance

The July 2020 change reflects ESIC’s move toward more digital and validated employer workflows.

The manual provides screenshots and detailed steps for mobile-number seeding, bank-account seeding, existing Insured Person updates and OTP validation.

Modern digital compliance depends heavily on accurate source information. An incorrect field can prevent the completion of a process or create future correction work.

Employers should therefore treat employee master data as an important component of statutory compliance.

Official ESIC Resources

The official ESIC circular dated 29 June 2020 is the primary source for the mandatory mobile and bank requirement effective from 1 July 2020.

View the official ESIC circular dated 29 June 2020

ESIC also published a detailed employer-portal manual created on 1 July 2020 explaining mobile-number and bank-account seeding procedures.

View the official ESIC Mobile and Bank Account Details manual

The official ESIC website provides additional information and employer services.

Visit the official ESIC website

Raj Consultancy Labour Law Compliance Support

Businesses that require support with labour-law compliance, ESIC records, statutory registrations, payroll documentation or employee compliance can review Raj Consultancy’s service resources.

Raj Consultancy Services Raj Consultancy Labour Law Compliance Services

Professional support can be useful when historical ESIC records contain incomplete mobile information, incorrect bank details, duplicate entries or multiple employee-registration periods.

Frequently Asked Questions

When did ESIC mobile and bank details become mandatory?

ESIC Mobile Number Bank Details Mandatory requirements became effective from 1 July 2020.

When was the ESIC circular issued?

The circular was dated 29 June 2020.

Why did ESIC introduce the requirement?

ESIC stated that the objective was to improve the efficiency of benefit disbursement, including claim reimbursement, and bring transparency.

Was a mobile number mandatory for new Insured Person registration?

Yes. The circular made the mobile number a mandatory field for registering a new Insured Person.

Was bank information mandatory?

Yes. Bank-account details became a prerequisite in the new Insured Person registration process.

What bank details were entered?

The process included IFSC, account number and account type, along with supporting bank documentation.

Was the mobile number validated?

Yes. The ESIC system validated the mobile number and included OTP verification in certain duplicate or ambiguous cases.

Could the same mobile number be linked to more than one Insured Person?

The system generally flagged duplicate mobile numbers. In specified cases, an employer could proceed after certifying correctness and completing the prescribed OTP validation.

What happened if the bank account already belonged to another person?

The ESIC system was designed to check bank-account information and prevent duplicate bank credentials in the database.

Was documentary evidence required for bank details?

The official implementation manual states that an attested copy of the bank passbook or cheque leaflet had to be scanned and uploaded as documentary evidence for bank-account seeding.

Could existing Insured Persons update their mobile number?

Yes. The employer portal included a separate “Update Particulars of Insured Person” process for updating existing mobile information.

Could existing Insured Persons update bank information?

Yes. The ESIC manual provides a bank-detail update workflow for existing Insured Persons.

Why was correct information important?

ESIC placed responsibility on employers for entering correct information, and the validation process was designed to reduce incorrect or unreliable data.

Seven Essential Compliance Checks

The ESIC Mobile Number Bank Details Mandatory requirement can be reviewed using seven practical checks.

1. Check the effective date: Confirm that the requirement relates to the period beginning 1 July 2020.

2. Check the employee: Determine whether the employee was being newly registered or enrolled using an existing Insurance Number.

3. Verify the mobile number: Confirm that the correct employee mobile number was entered and validated.

4. Check OTP requirements: Where duplication or ambiguity existed, verify that the prescribed OTP validation was followed.

5. Verify IFSC: Confirm that the correct bank IFSC was entered and validated.

6. Verify account details: Check the account number, account type and bank document against the employee’s records.

7. Preserve evidence: Retain relevant employee documents and confirmation records supporting the ESIC registration or update.

This approach creates an easy and reliable process for reviewing historical ESIC data and reduces the risk of incomplete or incorrect information.

Benefits Of Accurate ESIC Data

Accurate employee data can make ESIC administration more efficient. Correct mobile information supports digital validation and communication, while correct bank information supports benefit-related transactions.

Accurate records also reduce the risk of delays caused by duplicate or incorrect information.

From an employer perspective, a well-maintained database makes statutory reviews easier and creates a stronger record for audits.

Negative Consequences Of Incorrect ESIC Details

Incorrect mobile or bank information can create unnecessary administrative difficulties. A wrong mobile number may require correction, while a wrong bank account or IFSC can create problems with benefit-related payment processing.

Duplicate information can trigger system alerts and require additional validation.

Incomplete documents can also delay completion of the bank-detail process.

These are preventable issues when HR teams collect and verify employee information before submitting the registration.

Importance For HR And Payroll Teams

ESIC Registration 01-07-2020 is especially important for HR and payroll professionals maintaining historical employee files.

The July 2020 process demonstrates why employee master data should be checked before statutory registration. Mobile number, Insurance Number and bank information all became connected with the digital registration workflow.

Payroll teams should also maintain records of corrections when employee details change. An employee may change a mobile number or bank account, and the employer should use the prescribed portal process for updating the ESIC record.

Conclusion

ESIC Mobile Number Bank Details Mandatory is an important historical ESIC compliance update that became effective from 1 July 2020. The circular dated 29 June 2020 made mobile number and bank-account information a mandatory prerequisite for registering an employee as an Insured Person.

The ESIC Mobile Number Mandatory process required the employer to provide a correct mobile number and validate it through the ESIC system. Duplicate or ambiguous entries could trigger an alert and, in specified circumstances, OTP verification.

The ESIC Bank Details Mandatory process required the employer to enter the IFSC, account number and account type and upload supporting bank documentation. ESIC introduced these controls to improve data reliability and support efficient disbursement of benefits and claim reimbursements.

The ESIC Registration 01-07-2020 workflow also covered employees who already had an Insurance Number and included procedures for updating existing Insured Person information.

ESIC Insured Person Mobile Number information could be updated through the employer portal, while bank details could also be seeded or updated using the relevant workflow.

For historical compliance, the exact circular and the official ESIC implementation manual are valuable references. Employers reviewing old records should verify the effective date, registration status, mobile validation, IFSC, account number, documentary evidence and update history.

Using incorrect or incomplete information can result in alerts, correction requirements and avoidable administrative delays. Maintaining accurate employee records is therefore an important and positive statutory-compliance practice.

This article describes the historical ESIC requirement introduced in 2020. For current ESIC registration and employer-portal procedures, the latest official ESIC instructions should always be checked before processing a registration or changing employee records.