Assess eligibility for branch registration

• Determine if the new branch employs 10 or more workers, or if it’s part of a covered organization.
  
• Branches in different states or with separate operations may require individual sub-code registration.
  
• Confirm that the branch falls under the purview of the ESIC Act, 1948.
  
• Check whether employees in the branch fall within the wage threshold limit.
  
• Only eligible branches are allowed to be separately registered under ESIC.
  

Log in using main establishment credentials

• Use the employer login credentials from the head office ESIC account.
  
• Access the ‘Sub-unit Registration’ or ‘Add Branch’ option from the employer dashboard.
  
• Ensure the head office registration is active and compliant before proceeding.
  
• Keep branch-specific documents ready for data entry and uploading.
  
• Only authorized users can initiate branch-level registrations.
  

Fill out branch registration form

• Enter the branch address, number of employees, and start date of operations.
  
• Include employer details and nature of business at the branch.
  
• Provide information about employees working in the branch.
  
• Verify all information for correctness before final submission.
  
• Attach required documents such as address proof and HR records.
  

Submit and generate sub-code

• Upon submission, a unique sub-code number is generated for the branch.
  
• This sub-code allows the branch to make contributions and file returns independently.
  
• The sub-code is linked to the main code of the parent establishment.
  
• Use the sub-code for branch-level employee registration and compliance.
  
• Keep a record of the sub-code for administrative and audit purposes.
  

Ensure compliance from the branch

• The branch must begin monthly contributions and return filing under the sub-code.
  
• Maintain separate employee records for the branch location.
  
• Ensure contributions are paid by the 15th of each month.
  
• Coordinate with the head office to maintain consolidated compliance.
  
• Update any changes to branch structure or operations as required.