Registering for PF & ESI, step by step
When registration becomes mandatory, where it happens, what documents the portals want, and what the first compliant month after registration looks like: the employer's setup guide.
Rates and thresholds re-verified 27 July 2026. Statutory figures change by notification, so always confirm against the current official source before acting.
When registration triggers
EPF registration is mandatory once an establishment employs 20 or more persons (counting broadly — contract and casual staff included), with voluntary registration available below the threshold. ESI registration triggers at 10 employees in most states (20 in some) within implemented areas, covering employees earning up to ₹21,000. Two truths worth internalising: the count is of persons employed, not of persons above any wage level, a 22-person establishment with 20 high earners still registers for EPF; and the obligation dates from crossing the threshold, not from noticing it — late registration collects arrears from the trigger date, with interest and damages. Growing establishments should therefore watch the count prospectively: registration a hire early is cheap, a year late is not.
Where it happens and what it needs
Both registrations are online. EPF registration runs through the Shram Suvidha portal's common registration, yielding the establishment code; ESI runs through the ESIC portal, yielding the 17-digit employer code. The document set is similar: incorporation proof (certificate, partnership deed or GST/licence for proprietorships), PAN, address proof, bank details, digital signature of the authorised signatory, and employee particulars — count, wages, dates of joining. Approvals are typically quick when documents are consistent; mismatched addresses and names between documents remain the classic delay. Registration itself is the establishment's act — software prepares and maintains everything around it, but the portal application is yours or your consultant's.
The registration path, end to end
-
1
Confirm applicability
Count persons employed (direct, contract, casual) against the thresholds: 20 for EPF, 10 for ESI in most states (20 in some), within ESI-implemented areas. Date the crossing; that date anchors everything.
-
2
Assemble the documents
Incorporation proof, PAN, address proof, bank details, authorised signatory's digital signature, and employee particulars with wages and joining dates — checked for consistency across documents before anything is filed.
-
3
Apply on the portals
EPF through Shram Suvidha's common registration for the establishment code; ESI through the ESIC portal for the 17-digit code. Your consultant can file both; the establishment signs.
-
4
Enrol the workforce
Generate or link UANs (employees with prior PF history link their existing UAN; ask at onboarding), obtain ESI numbers, and record nominee details. Day-one enrolment for future joiners becomes part of onboarding from here.
-
5
Run the first compliant month
Compute contributions from the applicability date, generate the first ECR and ESI files, upload and pay by the 15th, and archive the challans. Arrears from trigger date to registration date, if any, clear now, with the trail kept.
A worked example
A bootstrapped D2C brand grows from 14 to 21 people in March: the 21st hire being a part-time warehouse assistant nobody thought of as 'headcount'. EPF applicability dates from March; the founders begin registration in April when their CA runs the count, obtain the code in two weeks, and clear March-April arrears with the first ECR. Cost of the month's drift: modest interest and an afternoon of paperwork. Their competitor who crossed 20 in January and noticed at a September due-diligence: eight months of arrears with damages, discovered by an investor's lawyer, same rule, very different invoice. The difference was a monthly headcount check that takes thirty seconds.
Figures are illustrative, for mechanism only. Verify current rates and your own structure before relying on any number.
The startup pattern: register before you must
For a company that expects to scale, early voluntary EPF registration is usually the cheaper path: senior hires arrive with UANs and the expectation of continuity, contribution history builds cleanly from the start, and the threshold crossing becomes a non-event instead of a project. The counterargument (avoiding the compliance overhead while small) underweights how light the overhead is with computed payroll, and overweights how disruptive mid-growth registration is. The decision deserves ten minutes with your CA at incorporation, not a scramble at employee nineteen.
After registration: the duties that actually recur
Registration is a day; the duties are monthly. ECR upload and PF payment by the 15th; ESI contribution and filing by the 15th; enrolment of every joiner from day one; exit marking for leavers (delayed exit-marking is why ex-employees' withdrawals stall and turn into calls to your HR); nominee and KYC maintenance so claims never bounce; and returns per each scheme's calendar. Every one of these is a generated artifact or a recorded event in a computed payroll, which is the honest answer to 'how much work is compliance': very little, if the system does the arithmetic, and endless, if a person does.
How payroll software applies this
PeopleDeck cannot press the portal buttons for you (registration is by design the establishment's act) but it removes every reason registration goes wrong: headcount visible against the thresholds as you hire, UAN and ESI capture built into onboarding, day-one contributions computed from each joiner's actual dates, and the first month's ECR and contribution files generated as routinely as the fiftieth's. The compliance clock starts at the trigger; the system keeps you aware of where the clock stands.
Go deeper: PF & ESI compliance · Onboarding · PF calculation
Primary sources: Shram Suvidha portal · EPFO · ESIC
Maintained by Databus Technology Solutions against the source notifications; the verification date above is refreshed whenever a figure changes. This guide explains rules and mechanics; it is not legal or tax advice. PeopleDeck applies statutory rates and generates upload-ready files; it never files returns on your behalf, and positions on contested questions belong with your consultant.
Frequently asked questions
Is PF registration needed below 20 employees?
Not mandatorily, but voluntary registration is available with employee and employer consent, and startups that expect to cross 20 often register early: it simplifies hiring (candidates ask for UAN continuity) and avoids the mid-year scramble at the threshold.
Do contract workers count toward the thresholds?
Broadly, yes — persons employed through contractors count toward the establishment's strength for coverage purposes, and principal-employer exposure attaches to their contributions. Count everyone who works, not everyone on your payroll.
What is the timeline for registering after crossing the threshold?
Effectively immediate — ESI's framework expects registration within 15 days of applicability, and EPF liability runs from the date coverage applies. The safe operating rule: begin the application the month the count crosses, and treat the trigger date as the compliance start date regardless of when the code arrives.
What happens right after registration?
Contributions are due from applicability: UANs generated or linked for each employee, ESI numbers issued, the first ECR and contribution files uploaded, and payments by the 15th of the following month. The first month sets the pattern — get it computed properly rather than approximated.
Can an establishment deregister if headcount falls?
EPF coverage, once applicable, continues even if strength later falls below 20: the 'once covered, always covered' principle. ESI applicability similarly persists per its rules. Plan registration as a one-way door, because it is one.
Do branches in other states need separate registrations?
EPF runs on establishment codes with sub-codes possible for branches; ESI requires registration reflecting each implemented area of operation. Multi-state growth means keeping the registration map current, typically your consultant's checklist, fed by your headcount data.
Can we run payroll while registration is pending?
Yes, and you should: pay normally, compute contributions from the applicability date, and remit with the first ECR once the code arrives, clearing any interim arrears with the trail kept. What you must not do is treat the pending application as a contribution holiday; liability runs from the trigger, not the approval.
Registered right, compliant from month one.
Applied on every payslip, files generated for upload — per employee, per month.
Start free