How to Set Up Payroll for a Startup in India

How to Set Up Payroll for a Startup in India

Learning how to set up payroll for a startup in India is one of those founder tasks that looks like a two-hour job and turns out to be a system you will live with for years. The first salary transfer is easy. What is hard is everything wrapped around it: the registrations that quietly become mandatory as you hire, the salary structure you accidentally lock yourself into, the deductions you were supposed to deposit last month, and the records an auditor or a departing employee will ask for eighteen months from now.

This guide is written as an operating manual. It assumes you are a founder, a first HR hire, or a finance generalist who has been handed payroll and told to "figure it out." It walks from the pre-requisites you need before you can legally pay anyone, through designing a salary structure, running your first cycle end to end, and then scaling that machine from one employee to a hundred without it breaking.

One important framing note before we start. Payroll in India sits on top of a stack of central and state laws whose rates, wage ceilings, thresholds and filing dates change. This article explains the mechanics, the logic and the sequence. It deliberately avoids stating current rates and limits as fixed facts, because they move. Before you act on anything here, verify the present position on the relevant government portal or with your chartered accountant, company secretary or labour law consultant.

What "Payroll" Actually Means in an Indian Startup

Most first-time founders think payroll means "calculate salary, transfer money." That is roughly a fifth of it. Payroll in the Indian context is a monthly compliance cycle with a payment event attached.

A complete payroll function covers:

• Compensation design — what you promise, how it is broken into components, and how CTC translates into gross and net pay.
• Data management — employee master records, joining and exit dates, bank details, statutory identifiers, tax declarations and proofs.
• Attendance and leave inputs — loss-of-pay days, unpaid leave, overtime where applicable, shift or field allowances.
• Calculation — earnings, employer contributions, employee deductions, arrears, one-time payments and recoveries.
• Disbursement — salary transfers through your bank, usually via a bulk upload or an API-linked payout file.
• Statutory deposits and returns — provident fund, employee state insurance, professional tax, labour welfare fund, tax deducted at source, each with its own portal, rhythm and due date.
• Documentation — payslips, statutory registers, muster rolls, wage registers, Form 16 at year end, and full-and-final settlements on exit.
• Reporting — payroll cost by team for your board deck, provisioning for gratuity and leave encashment, and reconciliations for your auditor.

If you only build the calculation and disbursement pieces, you have built an expensive spreadsheet, not a payroll system. The compliance and documentation layers are where startups get hurt, usually two or three years later during a due diligence exercise when someone asks for records nobody ever created.

Why Getting Startup Payroll India Right Early Matters

Payroll debt behaves like technical debt. It compounds quietly and the interest is paid at the worst possible moment.

Three moments where early payroll shortcuts become expensive:

1. Fundraising due diligence. Investor counsel will ask for PF and ESI challans, TDS returns, registration certificates and employment agreements. Gaps become conditions precedent, indemnities, or a haircut.
2. An employee dispute. A terminated employee who claims unpaid wages or wrongly withheld dues puts your records on trial. Reconstructed evidence is weak evidence.
3. A departmental inspection or notice. Late deposits attract interest and damages. Non-registration when you crossed a threshold can trigger retrospective demands covering the entire period you should have been registered.

None of these are exotic. They are the ordinary lifecycle of a company that hires people. The good news is that a payroll setup done properly at five employees costs you a few days of work and scales almost unchanged to a hundred.

Pre-Requisites: What You Need Before Your First Payroll Run

You cannot set up payroll for a startup in India in isolation from your entity setup. Some of these you already have from incorporation; others you need to actively obtain.

Entity-Level Basics

• A registered legal entity. Private limited company, LLP, one person company, partnership or proprietorship. Your obligations differ slightly by form, but every one of them can employ people and every one of them triggers payroll compliance.
• PAN of the entity. Issued at incorporation for companies and LLPs. This is your tax identity.
• TAN (Tax Deduction and Collection Account Number). This is separate from PAN and is specifically required to deduct and deposit TDS, including TDS on salary. You cannot file salary TDS returns without it. Apply early; it is a common bottleneck for startups who realise in month one that they need to deduct tax and have no TAN.
• A current account in the entity's name. With net banking enabled and, ideally, bulk payment or salary upload functionality. Ask your relationship manager specifically about bulk transfer file formats and per-transaction limits before your first cycle.
• GST registration, if applicable to your business. Not a payroll requirement, but it interacts with contractor invoicing and reimbursements, so know your position.

Labour and Establishment Registrations

• Shops and Establishments registration. This is a state-level registration for commercial establishments and is typically the first labour registration a startup needs. It generally applies from the point you commence business at a premises, often within a defined number of days of starting operations, and it governs working hours, weekly offs, leave entitlements and record-keeping in that state. Registration is per state and frequently per establishment, so a second office in another state usually means a second registration.
• Factories Act registration, if you operate a manufacturing facility meeting the applicable criteria. Most software and services startups will not need this; hardware, food, and manufacturing startups often will.
• Professional Tax (PT) registration. A state-level tax on employment, levied by some states and not by others. Where it applies, you typically need both an employer registration (for the entity's own liability) and an enrolment or registration to deduct PT from employee salaries, then deposit and file returns on a state-specified frequency.
• Labour Welfare Fund (LWF). Applicable in some states only, usually a small contribution from both employee and employer, collected at a state-specified periodicity — often half-yearly or annually rather than monthly. Small in rupee terms; still a compliance item that shows up in audits.
• Provident Fund (EPF) registration. Becomes mandatory once your headcount crosses the threshold specified under the Employees' Provident Funds and Miscellaneous Provisions Act for your class of establishment. Voluntary coverage before that threshold is also possible and many startups opt in early because candidates expect it.
• Employees' State Insurance (ESI) registration. Becomes mandatory once your headcount in a notified area crosses the applicable threshold, and applies to employees earning below a specified monthly wage ceiling. Note the two-part logic: the establishment gets covered based on headcount; individual employees get covered based on their wages.

Verify current thresholds, wage ceilings and contribution rates for EPF, ESI, PT and LWF on the relevant government portals before you register or calculate. They are revised from time to time and vary by state.

Registration Trigger Table

The table below summarises the typical logic of when each registration becomes relevant. Treat the "trigger" column as the shape of the rule, not the current numeric value.

The Registration Sequencing Mistake

The most common ordering error is to defer all labour registrations until "we have enough people." The problem is that some of these trigger on the day you cross the line, not at the end of the year, and coverage is often retrospective from the trigger date. If you cross a PF threshold in June and register in December, you may still owe contributions from June, plus interest and damages, and you now have to recover the employee share from people who already received their full salary.

The safer approach: identify which registrations you will need at ten and twenty employees, and start the paperwork when you are two or three hires away, not two or three hires past.

Designing Your First Salary Structure

Salary structure design is where founders create problems that take years to unwind. Once you have told an employee their basic salary is a certain number, reducing it is legally and practically difficult. Design it once, deliberately.

CTC vs Gross vs Net: The Three Numbers Everyone Confuses

• CTC (Cost to Company) is everything the company spends on an employee in a year, including employer contributions to PF, gratuity provisioning, insurance premiums and any variable pay. It is a budgeting concept, not a legal one.
• Gross salary is the sum of the earnings components before employee-side deductions — basic, HRA, allowances, and so on.
• Net salary (take-home) is gross minus employee PF, employee ESI where applicable, professional tax, TDS, and any voluntary or recovery deductions.

The gap between CTC and take-home surprises new employees constantly, and unmanaged, it becomes a trust problem in month one. Show candidates a full breakup at the offer stage. A one-page structure sheet that walks from CTC down to estimated monthly take-home prevents more grievances than any policy document you will write.

Typical Components of an Indian Salary Structure

How to Choose the Basic Salary Percentage

Basic salary drives PF contributions, gratuity accrual, and often overtime and statutory bonus calculations. Set it low and you reduce immediate employer cost but create risk under wage-definition rules. Set it high and your PF outflow and gratuity liability rise, and employee take-home falls.

Three practical considerations:

1. The wage-definition question under the labour codes. India's consolidated labour codes introduce a standardised definition of "wages" with a structural principle: excluded allowances cannot exceed a specified proportion of total remuneration, and any excess is added back into wages for the purpose of statutory calculations. The practical implication is that structures engineered to keep basic very low relative to allowances become less effective, and PF, gratuity and related liabilities rise. Because implementation timing and state-level rules have moved, confirm the current position for your states — but design your structure so that a shift toward a higher effective wage base would not blow up your cost model.
2. Employee take-home preference. Junior employees usually prioritise cash in hand. Senior employees often prefer higher retirement contributions and structured benefits. A single rigid structure across all levels satisfies nobody perfectly.
3. Consistency and defensibility. Whatever ratio you choose, apply it consistently through a policy rather than negotiating it per candidate. Ad hoc structures are an operational nightmare at fifty employees and look arbitrary in a dispute.

Worked Example 1: Building a Structure from CTC (Illustrative)

These numbers are hypothetical and used only to show the arithmetic. Do not treat the rates as current or applicable to you.

Assume an annual CTC of Rs 9,00,000 for an employee in a state that levies professional tax, with employer PF applied on basic, and gratuity provisioned in CTC. Assume, purely for illustration, an employer PF rate of 12 percent of basic and a gratuity provision of roughly 4.81 percent of basic.

Step 1 — Set basic at 50 percent of gross. We need to solve backwards, because CTC includes employer-side costs that are not part of gross.

Let annual gross = G, and basic = 0.5G.

CTC = G + employer PF + gratuity provision CTC = G + (0.12 x 0.5G) + (0.0481 x 0.5G) 9,00,000 = G + 0.06G + 0.02405G = 1.08405G G = 9,00,000 / 1.08405 ≈ Rs 8,30,220 per year, or about Rs 69,185 per month.

Step 2 — Split the gross.

Step 3 — Estimate take-home.

The lesson from this example is not the specific numbers. It is that the employee sees Rs 75,000 a month in the offer letter and roughly Rs 64,800 minus tax in the bank. Explain that gap before they join, not after.

Should You Cap PF at the Statutory Wage Ceiling?

Provident fund law contemplates a wage ceiling for mandatory contribution purposes, with the option for employers and employees to contribute on higher wages. Startups take one of three approaches:

• Contribute on actual basic, uncapped. Higher employer cost, higher employee retirement corpus, simpler to explain, and generally more defensible.
• Restrict to the statutory ceiling. Lower cost, lower take-home impact, but you need to document the policy clearly and apply it consistently.
• Mixed by grade. Operationally messy; avoid unless there is a strong reason.

Whichever you choose, write it into your compensation policy and apply it uniformly to new hires. Changing the approach later for existing employees is where disputes start, and reducing an existing contribution basis carries its own legal complications.

Employee Data You Must Collect Before the First Payroll

Payroll runs on data. Collecting it properly at onboarding takes fifteen minutes per employee. Chasing it later takes weeks and is the single biggest cause of delayed first payrolls at startups.

The Onboarding Data Checklist

Identity and statutory identifiers

• Full name exactly as it appears on PAN and Aadhaar (mismatches break TDS credit and PF transfers)
• PAN card copy and number
• Aadhaar number, where required for PF and ESI linkage
• Universal Account Number (UAN) if the employee has previous PF-covered employment
• Previous employer's PF member ID, if relevant to transfer
• Date of birth and date of joining, both stated identically everywhere

Banking

• Bank account number and IFSC code
• Account holder name as per bank records
• A cancelled cheque or bank statement header for verification

Employment terms

• Signed offer letter and employment agreement
• Designation, department, reporting manager, work location and state (this determines PT, LWF and Shops and Establishments applicability)
• Confirmed CTC and the agreed salary structure breakup
• Probation period and confirmation date, if applicable

Statutory and benefits forms

• PF nomination and declaration form
• ESI declaration form with family details, where ESI applies
• Gratuity nomination
• Group insurance nomination and dependant details, if you provide cover

Tax

• Choice of tax regime for the financial year
• Investment and expense declaration at the start of the year
• Previous employer income and TDS details for mid-year joiners, so that year-to-date tax is computed correctly rather than under-deducted

The Mid-Year Joiner Trap

A mid-year joiner who does not declare previous employer income gets under-deducted TDS all year, because your system computes tax as if this is their only income for the full year with full slab benefit. In March, either you deduct a painfully large amount in one month, or the employee gets a tax demand later and blames payroll.

Make previous-employer income declaration a standard onboarding field, not an optional one. Ask for it in writing, record the response even if the employee declines to share, and recompute when they do.

Data Hygiene Rules Worth Enforcing from Day One

1. One source of truth for employee master data. Not three spreadsheets and a WhatsApp thread.
2. Never edit a past payroll month's data. Correct it in the current month as an arrear or recovery, with a note.
3. Keep a dated audit trail of salary revisions, including the approval.
4. Store documents in a structured folder or HRMS, not in individual inboxes.
5. Restrict access. Payroll data is sensitive personal data; treat it accordingly, and be aware that India's data protection framework imposes obligations on how you collect, store and process it.

Choosing Your Pay Cycle and Cut-Off Dates

The pay calendar is a small decision with large operational consequences. Get it wrong and every month becomes a fire drill.

The Core Trade-Off

There are two broad models:

• Pay on the last working day of the month. Employees love it. It means your attendance cut-off has to be earlier in the month, so the last several days are estimated and adjusted next month.
• Pay in the first week of the following month. Gives you a clean full-month attendance cycle and time to compute accurately. Employees adjust quickly if it is stated clearly in the offer letter.

Most Indian startups settle on paying between the last working day and the seventh of the following month. What matters more than the exact date is that it never moves.

Defining Your Cut-Offs

Write down and publish these dates:

Practical Calendar Rules

• Account for bank holidays and weekends. If your pay date falls on a Sunday, decide in advance whether you pay before or after, and say so in policy.
• Build a buffer for the first three cycles. New payroll setups always surface data problems.
• Do not run payroll on the same day you upload to the bank. Approval and upload should be separate days with separate people involved wherever headcount allows.
• Separate the person who prepares payroll from the person who approves the bank transfer. Even in a five-person company, this basic control matters.

How to Set Up Payroll for a Startup in India: The Step-by-Step First Run

Here is the sequence for your first cycle, assuming registrations are in place or in progress.

Step 1: Lock the Employee Master

Build a single sheet or HRMS record with every active employee: employee code, name, DOJ, department, location and state, CTC, component-wise structure, bank details, PAN, UAN, PF applicability flag, ESI applicability flag, PT state, and tax regime choice.

Reconcile the headcount against your offer letters and your appointment records. A missing person or a duplicate here propagates through everything downstream.

Step 2: Collect and Freeze Inputs

Pull the month's variable inputs:

• Attendance and loss-of-pay days
• New joiners with pro-rated pay from date of joining
• Exits with pro-rated pay to last working day, plus notice pay or recovery
• Salary revisions and arrears
• Approved reimbursement claims
• Any one-time payments: joining bonus, referral bonus, incentive
• Any recoveries: salary advance, asset recovery, notice shortfall

Freeze these on the cut-off date. "Just one more change" is how payroll errors happen.

Step 3: Compute Earnings

For each employee:

1. Start with the monthly structure from the master.
2. Pro-rate for partial months using a consistent basis. Decide whether you use calendar days or working days, write it into policy, and never switch mid-year. Mixed bases produce inconsistent results that employees notice.
3. Apply loss of pay on the same basis.
4. Add arrears, one-time payments and approved reimbursements.
5. Arrive at gross earnings for the month.

Step 4: Compute Employer Contributions

• Employer PF on the applicable wage base, subject to your capping policy.
• Employer ESI for employees under the wage ceiling.
• Note that PF employer contribution is split between the pension component and the provident fund component, plus administrative charges. Your ECR file handles this split, but understand it, because it appears in reconciliations.
• Accrue gratuity as a provision. It is not a monthly cash outflow but it is a real liability that grows.

Step 5: Compute Employee Deductions

• Employee PF share on the applicable wage base.
• Employee ESI share where applicable.
• Professional tax as per the slab of the employee's work state.
• Labour welfare fund where applicable and in the relevant month.
• TDS on salary, computed as estimated annual tax divided across remaining months of the financial year.
• Voluntary deductions: voluntary PF, NPS contributions, loan or advance recovery.

Step 6: Produce the Payroll Register and Review

Generate a register showing every employee with all earnings, deductions, employer contributions, and net pay. Then review it properly:

• Compare net pay against last month for every employee and investigate any variance beyond a threshold you set, say five percent.
• Check that every new joiner appears and every exit is either paid correctly or excluded.
• Verify totals: gross, total deductions, total net, total employer cost.
• Sanity-check anyone with unusually high or low net pay.
• Confirm the sum of net pay matches the bank file total exactly.

This variance review is the highest-value fifteen minutes in the entire cycle. It catches almost every material error.

Step 7: Approve and Disburse

Get formal approval — an email or a system approval from a founder or finance lead is enough at small scale, but it must exist. Then generate the bank file in your bank's format, upload, and authorise.

Keep the approved register, the bank file and the bank confirmation together in one folder for the month. This trio is what an auditor asks for.

Step 8: Publish Payslips

Issue payslips promptly, ideally on or before pay day. A payslip should show earnings component-wise, deductions component-wise, employer contributions, LOP days, year-to-date figures, PF and UAN details, and the tax computation summary or a link to it.

Payslips are not optional courtesy documents. They are the employee's evidence of what they were paid, they are needed for loans, visas and rentals, and under wage legislation employers are expected to maintain and provide wage records.

Step 9: Deposit Statutory Dues and File Returns

Each statutory item has its own portal, its own file format and its own due date. At a high level:

Confirm the exact due dates applicable to you. Late deposits attract interest and, in the case of PF, damages that scale with the length of delay. Set calendar reminders that fire several days before each due date, not on the day.

Step 10: Close the Month

• Reconcile payroll cost in your books against the payroll register.
• Post the journal entries: salary expense, employer contribution expense, statutory liabilities, net pay clearing.
• Update the gratuity and leave encashment provisions.
• File the register, challans, returns and bank confirmations in the month's folder.
• Note anything that went wrong and fix the process before next month.

TDS on Salary: What Founders Actually Need to Understand

TDS on salary is where most startup payroll teams feel least confident. You do not need to be a tax expert, but you do need to understand the mechanic.

The Basic Mechanic

As an employer, you are required to estimate each employee's annual salary income, compute the tax payable on it after applicable exemptions and deductions, and deduct roughly one-twelfth of that tax each month, adjusting as circumstances change.

The key points:

• It is an estimate that gets refined. At the start of the year you use declarations. Around January you collect proofs. If declared investments are not evidenced, you recompute and the shortfall is deducted in the remaining months.
• The employee chooses a tax regime. India operates two personal income tax regimes with different slab structures and different treatment of exemptions and deductions. Employees must be given the opportunity to choose, and payroll must compute accordingly. Rules on default regime and switching have changed over time, so confirm the current position each year.
• You deposit monthly and report quarterly. TDS deducted is deposited using a challan, and quarterly statements in Form 24Q report the deduction details employee by employee.
• Form 16 is generated from those filings. Part A comes from the TDS system and reflects what was actually deposited and reported; Part B contains the salary and deduction breakup. If your quarterly returns are wrong, Form 16 is wrong, and employees cannot file their returns cleanly.

Where Startups Get TDS Wrong

• Deducting nothing all year because "everyone's tax is small," then facing a large March deduction and unhappy employees.
• Ignoring perquisites. Rent-free accommodation, company car, interest-free loans above thresholds, and certain ESOP events are perquisites that need valuation and inclusion.
• Not reconciling the sum of monthly deductions against the amounts reported in the quarterly returns, so Form 26AS credits do not match employee expectations.
• Missing the PAN. Deduction at a higher rate applies where a valid PAN is not furnished, which creates an awkward conversation and a correction cycle.
• Forgetting that TDS obligations apply to contractor payments too, under a different section with different rates and thresholds.

Worked Example 2: Mid-Year Joiner TDS Estimation (Illustrative)

Assume an employee joins on 1 October with a monthly gross of Rs 1,00,000. Assume, purely for illustration, that they declare previous employment income of Rs 5,00,000 with Rs 20,000 TDS already deducted by the former employer.

• Salary from your company for the remaining six months of the financial year: Rs 6,00,000
• Previous employer income: Rs 5,00,000
• Total estimated income for the year: Rs 11,00,000

Suppose the computed annual tax liability on Rs 11,00,000, after applicable standard deduction and any eligible deductions under the chosen regime, works out to Rs 90,000 in this hypothetical.

• Less TDS already deducted by previous employer: Rs 20,000
• Balance to be deducted by you: Rs 70,000
• Spread across your six remaining payroll months: approximately Rs 11,667 per month

Now consider what happens if the employee does not disclose the previous income. You would compute tax on Rs 6,00,000 only, which in this illustration might produce a much smaller monthly deduction — and the employee would face a substantial self-assessment tax payment plus possible interest when filing their return. Neither number here is a real tax computation; the point is the arithmetic of aggregation, not the figures.

Reimbursements and Flexible Pay Components

Reimbursements are a legitimate part of a well-designed structure, and also a common source of sloppiness.

The principle is simple: a reimbursement is not salary. It is the company paying back an expense the employee incurred on the company's behalf, or a benefit whose tax treatment depends on actual usage and evidence. If there is no bill, most such components lose their intended treatment and become fully taxable.

Components Startups Commonly Offer

• Telephone and internet reimbursement
• Fuel and vehicle running expenses, sometimes with driver salary in structured plans
• Books, periodicals and professional development
• Meal benefits, often via a card or voucher provider
• Leave travel allowance, claimable against actual travel within defined rules
• Health and wellness allowances, whose taxability depends on how they are structured

Rules That Keep Reimbursements Clean

1. Publish the eligibility and limits. Who gets what, and up to how much.
2. Require bills. Set a monthly or quarterly claim window and enforce it.
3. Approve before paying. A manager or finance approval on every claim.
4. Do not pay unclaimed balances as tax-free cash. Unclaimed amounts should either lapse or be paid as taxable salary.
5. Store the evidence. Bills are the only defence if the treatment is questioned.

Flexible Benefit Plans

Larger startups often introduce a flexible benefit plan where the employee allocates a portion of CTC across components — say, choosing more LTA and less special allowance. This is genuinely useful at scale but adds real administrative weight: an annual declaration window, mid-year change rules, a claim process, and a year-end true-up for unclaimed amounts.

Do not build a flexible plan at ten employees. Build it when you have a payroll system that can administer it and someone whose job includes running the annual cycle.

Contractors vs Employees: Why Misclassification Is Risky

Early-stage startups lean heavily on consultants, freelancers and "retainers." Some of that is genuine. Some of it is an employment relationship wearing a different label, and that is where the risk sits.

The Substance Test

Labour and tax authorities look at the substance of the relationship, not the title on the contract. Factors that point toward employment include:

• You control how, when and where the work is done, not just what the outcome is
• The person works fixed hours and is integrated into your team structure
• They use your equipment, your email, your systems
• They report to a manager and are subject to your performance process
• They work exclusively or near-exclusively for you, over a long period
• They receive a fixed monthly amount that looks like a salary
• They take leave under your leave policy

The more of these are true, the weaker the contractor characterisation.

What Goes Wrong

Practical Guidance

• Use contractors for genuinely project-based, outcome-defined, time-bound work.
• Have a proper services agreement with scope, deliverables, term and IP assignment. Do not reuse an employment template.
• Insist on invoices. A contractor who never invoices you is a warning sign.
• Deduct TDS under the correct provision for professional or contractual payments, and factor GST where the contractor is registered.
• Review your contractor list every six months. Anyone who has been full-time-equivalent for a year is a conversion candidate.
• For international contractors, get advice. Foreign exchange rules, permanent establishment exposure and the other country's employment law all come into play.

ESOPs and Equity: The Payroll Touchpoints

Equity is usually handled by the founders and the company secretary, but two moments land squarely in payroll.

At exercise. When an employee exercises options, the difference between the fair market value of the shares on the exercise date and the exercise price they pay is generally treated as a perquisite and taxed as salary income. That means payroll must include the perquisite value in the employee's salary for that period and deduct tax on it, even though the employee has received no cash. This creates the classic "tax on paper gains" problem, and it needs to be explained to employees well before they exercise.

At sale. When the employee eventually sells the shares, capital gains arise. That is the employee's own tax matter, not payroll's, but expect questions.

There are specific deferral provisions available to certain categories of eligible startups that allow the tax on exercise to be postponed. Eligibility is narrowly defined and the rules have evolved, so if you think you might qualify, get it confirmed rather than assumed.

Practical steps for payroll:

• Get the valuation done by a registered valuer in the manner the rules prescribe, before any exercise event.
• Coordinate the exercise calendar with payroll cut-offs so perquisite values reach payroll in time.
• Show the perquisite clearly on the payslip so the employee understands why their take-home dropped.
• Reflect it correctly in Form 24Q and Form 16 with the perquisite breakup.
• For exercises by employees who have already left, the tax mechanics differ; take advice.

Interstate and Remote Hires

Remote hiring is now default for many Indian startups, and it multiplies your compliance surface in a way that surprises founders.

The core principle: several payroll obligations follow the location where the employee actually works, not where your registered office is.

What Changes When You Hire in Another State

• Professional tax applies based on the employee's work state, at that state's slabs, deposited to that state, on that state's schedule. Some states levy no PT at all.
• Labour welfare fund applicability and rates are state-specific.
• Shops and Establishments registration may be required if you have an establishment in that state. A single home-based remote employee is a different fact pattern from an office; positions vary by state and this is worth checking rather than assuming.
• Leave entitlements under state Shops and Establishments Acts differ. Your leave policy should meet the most generous applicable requirement or be state-specific.
• ESI applicability depends on notified areas as well as headcount and wages.

A Workable Approach for Distributed Teams

1. Maintain a work-location field on every employee record and keep it current. Employees who move must inform HR.
2. Group employees by state and check the applicable registrations for each state where you have more than a token presence.
3. Standardise a single national leave policy set at or above the most demanding state requirement, so you are not running six policies.
4. If you are experimenting in a state with two employees, get a compliance opinion before you scale that location to twenty.
5. Consider whether an employer of record arrangement makes sense for very small footprints in distant states, while accepting the cost and the loss of direct control.

Spreadsheet vs Payroll Software: Making the Call

Every startup runs its first payroll in a spreadsheet. The question is when to stop.

Comparison

When to Switch

Honest triggers to move off spreadsheets:

• You have crossed roughly fifteen to twenty employees.
• You have become PF or ESI registered and are filing monthly.
• You employ people in more than one state.
• Payroll takes more than a day of someone's month.
• You have made an error that reached employees' bank accounts.
• You are raising a round and expect diligence.
• The only person who understands the payroll file is about to go on leave.

What to Look For in a Payroll System

• Handles Indian statutory calculations natively: PF, ESI, PT by state, LWF, TDS with both tax regimes
• Generates ECR files, PT challans and Form 24Q inputs in the required formats
• Supports flexible salary structures and component-level configuration
• Produces payslips and Form 16 with a proper breakup
• Integrates attendance and leave so LOP flows through automatically
• Employee self-service for declarations, proofs, reimbursement claims and documents
• Full-and-final settlement workflow
• Role-based access and an audit log
• Reports that map to your accounting entries
• Responsive support during month-end, when it actually matters

The Outsourced Option

Some startups hand payroll to their CA or a payroll bureau. That works if the volume is low and the arrangement is clearly scoped. Watch two things: you remain legally responsible for compliance regardless of who processes it, and you can end up with your employee data locked in someone else's spreadsheet. Insist on receiving the register, challans and returns every month, and keep your own copy.

Common First-Year Payroll Mistakes

These are the errors that show up repeatedly in first-year startup payroll.

1. Registering late. Crossing a PF or ESI threshold and registering months later, then facing retrospective liability and an impossible employee-share recovery.

2. Promising net salary. Telling a candidate "you will get Rs 80,000 in hand" instead of quoting CTC with a breakup. Once tax declarations change or a slab shifts, you either break the promise or absorb the cost forever.

3. No written salary structure. Just a CTC number in the offer letter with no component breakup, leaving the structure to be invented at first payroll and disputed later.

4. Inconsistent pro-ration. Using calendar days one month and working days the next, so two employees who joined on the same date get different amounts.

5. Ignoring the exit process. No full-and-final settlement checklist, no notice period recovery policy, no clarity on leave encashment, and unresolved dues that turn into legal notices.

6. Deducting but not depositing. Employee PF or TDS deducted from salary and not deposited on time. This is the most serious category of payroll error, because you are holding money that belongs to the employee and the government.

7. Skipping payslips. Paying salary by transfer with no payslip. Employees discover the gap when they apply for a home loan.

8. Never reconciling. Not tying payroll totals to the bank statement and the books, so errors accumulate invisibly.

9. Treating everyone as a contractor. Discussed above; the most expensive shortcut on this list.

10. No investment proof discipline. Accepting declarations in April and never collecting proofs in January, leaving TDS under-deducted and Form 16 unsupportable.

11. One person, no backup. A single individual owns payroll with no documentation. When they leave or fall ill, the cycle stalls.

12. Poor data security. Salary data in a shared drive everyone can open, or circulated over personal messaging apps.

13. Forgetting state-specific items. Missing PT and LWF for remote employees in states you did not think about.

14. No provisioning. Never provisioning for gratuity, leave encashment or bonus, so the liability lands as a surprise in an audit or on separation.

15. Changing structures mid-year without thinking. Restructuring components in November and creating messy year-to-date tax computations and confused employees.

A 30/60/90-Day Payroll Setup Roadmap

If you are starting from nothing, here is a sequence that works.

Days 1 to 30: Foundations

• Confirm PAN and apply for TAN if you do not have one
• Open or confirm a current account with bulk payment capability
• Complete Shops and Establishments registration for your primary location
• Check PT and LWF applicability for every state where you have people, and register where required
• Decide your compensation philosophy: basic percentage, HRA rule, PF capping policy, reimbursement components
• Draft standard offer letter and employment agreement templates, reviewed by a lawyer
• Build the employee master template with every field listed earlier
• Choose your pay date and publish the payroll calendar
• Decide spreadsheet or software, and if software, start the trial

Days 31 to 60: First Cycle

• Collect complete onboarding documentation from every existing employee
• Generate UANs or link existing ones where PF applies
• Configure salary structures for every employee and reconcile against offer letters
• Collect tax regime choices and investment declarations
• Run a parallel or dry-run payroll and reconcile it line by line
• Run the first live payroll with a deliberate two-day buffer
• Issue payslips
• Deposit statutory dues and confirm challans
• Post the accounting entries and reconcile against the bank

Days 61 to 90: Systematise

• Document the payroll SOP end to end, with screenshots if you are using software
• Assign a backup owner and have them run one cycle under supervision
• Set calendar reminders for every statutory due date for the next twelve months
• Build the month-end checklist below into your process
• Create the full-and-final settlement template and process
• Write the leave policy formally and align it with the statutory minimums in your states
• File the first quarterly TDS return, if a quarter has closed
• Review PF and ESI headcount against thresholds and plan the next registration
• Set a quarterly review to check whether structures, policies and registrations still fit

The Month-End Payroll Checklist

Print this, or put it in your project tracker as a recurring checklist.

Before the cut-off

• [ ] Attendance and leave data finalised and approved by managers
• [ ] New joiners added with complete data and correct date of joining
• [ ] Exits recorded with last working day and settlement inputs
• [ ] Salary revisions and arrears approved in writing
• [ ] Reimbursement claims submitted, approved and totalled
• [ ] Recoveries listed: advances, notice shortfall, asset dues
• [ ] Bank details verified for any new or changed accounts

Processing

• [ ] Earnings computed with consistent pro-ration
• [ ] Employer PF, ESI and gratuity provision computed
• [ ] Employee PF, ESI, PT and LWF applied by correct state
• [ ] TDS recomputed for the month, including any perquisites
• [ ] Payroll register generated

Review

• [ ] Month-on-month net pay variance reviewed for every employee
• [ ] Headcount reconciled: opening plus joiners minus exits equals closing
• [ ] Register totals cross-checked: gross, deductions, net, employer cost
• [ ] Bank file total equals register net pay total, to the rupee
• [ ] Formal approval recorded

Disbursement and after

• [ ] Bank file uploaded and authorised
• [ ] Payment confirmation saved
• [ ] Payslips published
• [ ] PF ECR filed and challan paid
• [ ] ESI contribution filed and paid
• [ ] PT deposited for each applicable state
• [ ] LWF handled if this is a contribution month
• [ ] TDS deposited via challan
• [ ] Journal entries posted and reconciled
• [ ] Provisions updated for gratuity and leave
• [ ] Documents filed in the month's folder
• [ ] Issues logged with a fix owner

Scaling Checkpoints: 10, 20, 50 and 100 Employees

Payroll does not scale linearly. It scales in steps, and each step has a characteristic set of problems.

The 10-Employee Checkpoint

This is where informality stops working. Somebody joins mid-month, somebody's increment is retrospective, somebody moves cities, and the spreadsheet acquires its first undocumented exception. Write down your rules now, while there are only ten cases to reconcile.

Also: check your PF and ESI position honestly. Counting rules for thresholds can include categories of workers founders do not think of. Ask your consultant to confirm your count rather than eyeballing it.

The 20-Employee Checkpoint

Now you are almost certainly filing monthly PF returns and possibly ESI. Manual filing at this size is feasible but consumes real time, and a missed deadline costs more than the software would.

This is also the point at which you should separate preparation and approval, and where the first serious employee grievance about a payslip line item usually arrives.

The 50-Employee Checkpoint

By fifty, payroll is a role, not a task. Expect:

• Multiple states, therefore multiple PT and LWF regimes
• Regular exits, therefore a settlement process that runs without ad hoc decisions
• An annual appraisal cycle with arrears across dozens of employees in one month
• Investor or auditor requests for payroll data with a short turnaround
• Enough salary bandwidth variation that inconsistent structures become visible internally

Do an internal payroll audit here: pick five employees at random and trace their offer letter, structure, monthly payslip, PF contribution, TDS and bank credit end to end. Any break in that chain is a process defect worth fixing before you double again.

The 100-Employee Checkpoint

At a hundred people you are running a small institution. Compensation bands, promotion rules, benefits governance and a compliance calendar owned by a named person are no longer nice to have. The payroll question shifts from "did we calculate correctly" to "are our policies consistent, defensible and affordable at 300 people."

Frequently Asked Questions

How much does it cost to set up payroll for a startup in India?

The direct costs are modest. Registrations are largely low-fee or nominal, though professional charges for a consultant to obtain them will vary by city and provider. Payroll software is typically priced per employee per month, so at ten employees it is a small line item. The real cost is time: the initial setup, and then the recurring monthly effort. That recurring effort is exactly what software and good process reduce.

When does PF registration become mandatory for a startup?

EPF coverage is triggered when your establishment's employee count crosses the statutory threshold applicable to your class of establishment. The count includes categories of workers that founders sometimes overlook, so verify it properly rather than estimating. You can also opt for voluntary coverage before you hit the threshold, which many startups do because candidates from larger companies expect PF. Once covered, coverage generally continues even if headcount later falls. Confirm the current threshold and the counting rules with your advisor.

What is the difference between CTC and take-home salary?

CTC is the total annual cost the company bears, including employer PF, gratuity provisioning, insurance and variable pay. Take-home is what actually reaches the bank account after employee PF, ESI where applicable, professional tax, TDS and any voluntary deductions. The gap is often meaningful — a large share of CTC never appears as monthly cash. Always give candidates a written breakup showing CTC, gross and estimated net so there is no surprise in month one.

Do I need to deduct TDS if all my employees earn below the taxable limit?

If an employee's estimated annual income after applicable deductions falls below the taxable threshold under their chosen regime, there is no tax to deduct and therefore nothing to deposit for them. But you still need to run the estimation, keep the computation on record, and revisit it if their salary or declarations change during the year. And once any employee crosses into taxable territory, you need TAN, monthly deposits and quarterly returns. Do not wait until then to apply for TAN.

Can I run startup payroll on a spreadsheet forever?

You can, but it stops being sensible somewhere between fifteen and twenty-five employees, and earlier if you are multi-state or PF and ESI registered. The failure mode is not that the spreadsheet suddenly breaks. It is that small errors accumulate, one person becomes irreplaceable, and statutory file formats and rate changes consume more time each month than the software would cost. Switch before an error reaches employees, not after.

What are the first payroll registrations I should get for my first employee?

For your very first employee, the essentials are usually your entity PAN, a TAN so you can deduct and deposit salary TDS, a Shops and Establishments registration for the state where you operate, and professional tax registration if your state levies it. PF and ESI generally come later as headcount grows, unless you opt in voluntarily. Because state rules differ, confirm your specific list for your state before hiring.

How do I handle payroll for employees working from different states?

Maintain an accurate work-location field for every employee, because professional tax, labour welfare fund, leave entitlements and certain registrations follow the state where the work is actually performed. Group your people by state, check what each state requires for your presence there, and register where needed. Standardise a national leave policy at or above the most demanding applicable requirement so you are not administering several policies. For a very small footprint in a distant state, an employer of record arrangement is worth pricing against the compliance effort.

Bringing It Together

Setting up payroll for a startup in India is not one decision. It is a sequence: get the registrations right, design a salary structure you can defend and afford, collect complete employee data before you need it, publish a pay calendar and hold to it, run a disciplined monthly cycle with a real review step, and deposit what you deduct on time, every time.

Do that consistently and payroll becomes background infrastructure — the thing that quietly works while you build the company. Skip steps and it becomes the thing that consumes your month-end, embarrasses you in diligence, and erodes employee trust one delayed payslip at a time.

Two closing reminders. First, verify every rate, threshold and due date against current government sources before you rely on it; this article gives you the mechanics and the sequence, not a substitute for professional advice on your specific facts. Second, build the process before you need it. Payroll set up properly at ten employees carries you to a hundred with only incremental change.

If you would rather not assemble all of this from spreadsheets and calendar reminders, CozyHR handles the Indian payroll stack in one place — salary structures, statutory calculations across states, payslips, filings support, employee self-service and the HR records that sit alongside them. If that sounds useful for where your team is right now, it is worth a look. If your spreadsheet is still working fine, keep it, and come back when it isn't.