Onboarding is rarely judged on the big things — the offer letter goes out, the laptop arrives, the induction happens. It is judged on the small things that quietly go wrong in the background: an employee whose attendance was never configured so their first week shows as absent, a salary structure copied from the wrong template, a PF number that never got captured and now blocks the first contribution. None of these are dramatic. All of them turn up exactly where an employee is most attentive — their first payslip.
The checklist, in the order it actually needs to happen
Before day one
- Offer terms finalised and consistent with the salary structure policy — not negotiated basic ratios that break the company's standard structure. See salary structure design in India.
- Employee ID and system access provisioned so day-one attendance has somewhere to record against.
- Reporting manager, department and designation confirmed — these drive approval chains and org reporting from the first day.
Statutory and compliance capture
- PAN, Aadhaar and bank details collected and verified before the first payroll run, not after.
- UAN (existing or new) captured for provident fund continuity — a missed UAN either creates a duplicate PF account or delays the first contribution.
- ESIC applicability checked against the current wage ceiling if the role is likely to qualify.
- Work state confirmed for professional tax, especially for remote hires or anyone working from a state different from the company's registered office — see professional tax in Indian payroll.
- Prior employment details where relevant to leave carry-in policy or gratuity continuity (for group transfers).
Attendance and leave setup
- Attendance method assigned from day one — kiosk, mobile, geofence — matching how the role actually works. See biometric vs mobile attendance for choosing the right method.
- Shift or roster assignment confirmed so the employee's schedule exists before their first clock-in, not after a payroll query. See shift and roster scheduling.
- Leave policy and starting balance set correctly — a new hire's leave should accrue from their joining date, not default to a full-year grant. See leave policy for Indian companies.
First payroll run
- Payable days calculated correctly for a partial first month — the single most common new-hire payslip error, where a mid-month joiner is paid for the full month or for the wrong number of days.
- Salary components verified against the structure template before the payslip is generated, not after the employee flags a discrepancy. See salary slip format in India.
Why this list is longer than most onboarding checklists
Most onboarding checklists are written from HR's side — documents collected, forms signed, induction scheduled. This one is written from payroll's side, because that is where an onboarding gap actually surfaces as a problem the employee experiences directly: a wrong or delayed first payslip. An employee will forgive a slow laptop delivery. A wrong first payslip is the thing they remember.
Making the checklist enforceable, not aspirational
A checklist in a document gets skipped under deadline pressure. The durable version lives in the system that actually runs payroll and attendance — where a new hire cannot generate a payslip until their salary structure, attendance method and statutory identifiers are captured, because the system requires it rather than trusting someone to remember it. That is the difference between a policy and a guarantee. If you are evaluating how a platform handles this end to end, attendance management and salary structure management cover the two halves that matter most at onboarding.
