First Payroll for Startup India: Step-by-Step Setup Guide

Running your first payroll for startup India feels like a small task until the last week of the month arrives. Suddenly you need registrations you have never heard of, salary structures nobody has written down, attendance data spread across chat messages, and a bank file that must be correct on the first try. Employees notice a wrong salary within minutes, and regulators notice a missed deposit within weeks.

This guide walks you through the whole journey in order. It starts with the registrations to consider, moves through employee data, salary structure, attendance cut-off, computation, TDS, disbursement and payslips, and ends with a filing calendar, a first-month checklist and the mistakes founders most often make.

A quick note before we begin. Statutory rules, thresholds, rates and due dates in India change from time to time and differ by state and by the nature of your business. Everything here is general guidance to help you plan. Please verify current rules with the relevant government portal, or with a chartered accountant or company secretary, before you act. Numbers in examples are illustrative only.

Why the first payroll matters more than the tenth

Your first payroll sets the pattern for everything that follows. The salary structure you pick becomes the template for offer letters. The cut-off date you announce becomes an expectation. The way you handle a correction in month one becomes the way your team believes corrections will always be handled.

There is also a compliance angle. Many obligations begin the moment you have your first employee, not when you feel "big enough". Late registration and late deposits usually attract interest or penalties, and unlike a product bug you cannot quietly patch them in the next release.

The good news is that payroll is a process, and processes can be designed. Once you build it well the first time, each later month takes hours instead of days.

Step 0: Decide what kind of engagement you actually have

Before you register for anything, be clear about who is on your payroll. Founders often mix three very different arrangements.

• Employees. People on your rolls with an employment relationship. Payroll, statutory deductions and payslips apply.
• Consultants or freelancers. Paid against invoices, usually with tax deducted at source under the relevant non-salary provisions. They are not on payroll.
• Interns. Treatment depends on whether they are paid a stipend, how the arrangement is documented and how your state and the applicable laws view it. Ask your advisor rather than assuming.

Labelling a full-time, fixed-hours, single-client worker as a "consultant" to avoid compliance is a risky shortcut. The nature of the work, control and exclusivity matter more than the label. If in doubt, take advice early.

Step 1: Registrations to consider before you pay anyone

Which registrations you need depends on your legal structure, your state, your headcount and your industry. Treat the list below as a discussion checklist for your advisor, not a final answer.

Business identity registrations

• Entity incorporation. A private limited company, LLP, partnership or proprietorship each has different payroll implications. Directors of a company, for example, may be paid as employees or as directors, and the treatment differs.
• PAN of the entity. Needed for almost everything, including tax deduction and filing.
• TAN. The Tax Deduction and Collection Account Number is required to deduct tax on salary and deposit it. Without it you cannot file quarterly TDS returns or issue TDS certificates properly.
• GST registration. Not a payroll registration, but often obtained at the same time. It matters for invoicing and input credit, so keep it in the same conversation.

Employment-related registrations

• Employees' Provident Fund (EPF). Generally applies once an establishment crosses a headcount threshold, and some establishments can register voluntarily. Check the current applicability rules and whether registering early makes sense for hiring and benefits.
• Employees' State Insurance (ESI). Applicability depends on headcount, location coverage and a wage ceiling for employees. Some of your employees may be covered while others are not, even within one office.
• Professional Tax (PT). A state-level levy. Some states charge it, some do not, and the slabs, registration process and return frequency differ. Employers commonly need both an enrolment and a registration certificate in states that levy it.
• Shops and Establishments registration. Most states require offices, shops and commercial establishments to register under their local act. It usually governs working hours, leave, holidays and record-keeping. Timelines for registering after you start operations vary by state.
• Labour Welfare Fund (LWF). A few states collect small periodic contributions from employer and employee. Check whether your state does.
• Gratuity and bonus. These are not registrations in the same sense, but you should know when they become applicable so you can plan the cost.

If you operate in more than one state, each state may bring its own set of requirements. That is a large topic on its own, so we will only mention it here and point you toward dedicated multi-state guidance rather than repeating it.

A simple way to sort your list

Write down the date each registration was applied for, the date it was granted and the login credentials owner. This small register saves hours later when an auditor, investor or new finance hire asks for it.

Step 2: Collect employee data the right way

Bad data is the single biggest cause of payroll errors. A misspelt name breaks a bank transfer. A wrong PAN breaks TDS credit. A missing UAN delays provident fund. Collect everything once, verify it, and store it in one place.

The employee master checklist

For each employee, collect:

• Full name exactly as on PAN and bank account
• Date of birth and gender
• Date of joining and confirmation date
• Designation, department and reporting manager
• Work location (city and state, which drives professional tax and shops act rules)
• PAN and Aadhaar details where required for statutory purposes
• Bank account number, IFSC and name on account
• UAN and previous PF member ID, if any
• ESI number, if previously covered
• Previous employer details, including income earned and tax deducted in the current financial year
• Tax regime choice communicated by the employee
• Emergency contact and address

Handle personal data responsibly

You are collecting identity and financial data. Limit access to people who genuinely need it, avoid sharing salary sheets on open chat groups, and keep a record of who has downloaded what. Data protection expectations in India are increasing, so build the habit now rather than after a complaint. Confirm current obligations with your legal advisor.

Verify, do not just collect

• Match the bank account holder name with the employee name. A small penny-drop or name-match check before the first transfer prevents returns.
• Ask for a cancelled cheque or bank statement page as proof.
• Cross-check PAN against the name on the offer letter.
• For employees who joined mid-year, insist on the previous employer's salary details so that tax is computed on the correct combined income.

Step 3: Salary structure basics

A salary structure is the recipe that converts an annual cost-to-company number into monthly components. You do not need a perfect design for month one, but you do need a consistent one. (For deeper thinking on how to design compensation packages, see our separate guidance on CTC design. This section only covers the basics you need to run payroll.)

Common components

• Basic salary. The foundation of the structure. Many statutory contributions and benefits are linked to it or to a wage definition that includes it.
• House Rent Allowance (HRA). A component that may be partially tax-exempt for employees who pay rent, subject to conditions and the tax regime they choose.
• Special or flexible allowance. The balancing figure that makes the total equal the intended CTC.
• Other allowances. Transport, telephone, meal or internet reimbursements, depending on your policy and tax treatment.
• Employer contributions. Employer share of provident fund, ESI where applicable, and possibly gratuity provisions.
• Variable pay or bonus. Paid on performance or on a schedule and taxed as salary when paid.

Fixed versus variable, gross versus net

Employees think in take-home terms. Employers think in cost-to-company terms. Your offer letter should show both, and your payslip should make the bridge obvious: gross earnings, then deductions, then net pay.

An illustrative structure

The figures below are illustrative only and are not a recommendation. They show how one monthly gross can be broken up.

Deductions on the payslip might then include the employee provident fund contribution, professional tax where applicable and TDS on salary. Net pay is gross minus these deductions. The exact amounts depend on your registrations, state and each employee's tax position, so treat the table as a layout, not as advice.

Rules of thumb for a young company

• Keep the number of components small. Ten allowances create ten places for errors.
• Write the structure into a short policy document so every offer letter follows the same logic.
• Decide early how you treat notice-period buyouts, joining bonuses and relocation payments.
• Decide how proration works. Calendar days or fixed 30 days? Pick one and apply it to everyone.

Step 4: Set your payroll calendar and attendance cut-off

Payroll is a monthly production line. If the inputs arrive late, the output is late. The fix is a written calendar that everyone follows.

A sample monthly calendar (illustrative)

Your dates will differ, and many startups pay on the last working day or the first of the next month. The point is that the cut-off is fixed, communicated and honoured.

Attendance cut-off, explained

A cut-off is the date up to which attendance, leave and other inputs count for this payroll. Anything after it goes into the next cycle as an adjustment. You have two common models.

• Same-month payroll. The cut-off is a few days before month end. Days after the cut-off are assumed present and corrected next month if needed.
• Arrears-based payroll. Salary for the completed month is paid in the following month, so there is no assumption.

Either works. What fails is having no rule, so that every month's payroll is delayed by "one more leave application".

Leave, holidays and loss of pay

Decide and document:

• How many leave types you offer and how they accrue
• Whether holidays and weekends inside a leave period count as leave
• How unpaid leave, called loss of pay, is calculated
• How half days and short leaves are handled
• How leave balances carry forward or lapse

Your state's shops and establishments rules may set minimum expectations, so align your policy with them.

Handling first-month joiners and leavers

A new joiner's first salary is prorated from the date of joining. An exit inside the month is prorated to the last working day, plus any final settlement items such as leave encashment, notice recovery or gratuity where applicable. Keep a simple full-and-final checklist even if nobody has left yet. You will be glad you did.

Step 5: Compute the payroll

Computation is where inputs turn into pay. Follow the same sequence every month.

1. Freeze inputs. Joiners, leavers, salary revisions, attendance, leave, overtime, reimbursements, bonuses, loans and advances.
2. Calculate paid days. Total days in the cycle minus loss-of-pay days.
3. Prorate earnings. Apply paid days over payable days to each fixed component.
4. Add one-time earnings. Bonuses, incentives, arrears and approved reimbursements.
5. Calculate statutory deductions. Provident fund, ESI where applicable, professional tax where applicable, labour welfare fund where applicable.
6. Calculate TDS. Monthly tax on salary based on projected annual income and declarations.
7. Apply other deductions. Loan recoveries, notice recovery, asset damage recovery only where policy and law allow.
8. Arrive at net pay. Gross minus all deductions.
9. Review variance. Compare with last month and investigate each large change.

A worked illustration

Assume, purely as an illustration, that an employee has a monthly gross of 60,000 rupees and takes 2 days of unpaid leave in a 30-day cycle.

• Paid days: 30 minus 2, so 28
• Prorated gross: 60,000 multiplied by 28 divided by 30, which is 56,000
• Deductions: assume statutory items and TDS total 7,000 for this example
• Net pay: 56,000 minus 7,000, which is 49,000

The numbers are made up to show the mechanics. Your actual deductions depend on registrations, wage definitions, state and tax position.

Wage definitions matter

Different laws define "wages" differently for the purpose of contributions and thresholds. An amount that counts towards provident fund may not count for ESI eligibility, and vice versa. Ask your advisor to confirm how each of your components is treated, and lock that mapping into your payroll system so it is applied automatically.

Build a review habit

Before releasing, run these checks:

• Total net pay compared with previous month, with reasons for changes
• Employees with zero or negative net pay
• New joiners and leavers listed and verified
• Duplicate bank accounts
• Employees with a missing PAN, bank detail or UAN
• Salary revisions applied from the correct month

Step 6: TDS on salary, explained simply

Tax deducted at source on salary is your responsibility as an employer once an employee's estimated taxable income crosses the applicable exemption level. You are effectively collecting income tax on behalf of the government, month by month.

How the monthly TDS logic works

1. Estimate the employee's total taxable salary for the whole financial year, including expected bonuses.
2. Subtract eligible exemptions and deductions based on the regime the employee has chosen and the proofs or declarations submitted.
3. Compute the annual tax on the result using the slabs of the chosen regime.
4. Add applicable cess and surcharge if any.
5. Subtract tax already deducted by a previous employer in the same year, if the details were provided.
6. Divide the remaining tax by the number of months left in the year to get this month's TDS.

The projection is refreshed whenever something changes: a raise, a bonus, a new declaration or proof submission. That is why TDS can look uneven from month to month.

Two regimes, one choice per employee

India offers more than one personal tax regime, with different slabs and different sets of allowed deductions. Employees usually tell the employer which regime they want for the year, and can generally change their mind when they file their own return. Ask each employee for a written choice at joining and at the start of every financial year. Confirm the current regime details, defaults and slabs on the income tax department's website before configuring your system.

What to collect from employees

• Regime choice
• Rent paid and landlord details, if claiming HRA
• Investment and deduction declarations, if on the regime that allows them
• Home loan interest details, if claiming
• Previous employer income and tax details for mid-year joiners

Declarations early in the year let you spread the tax evenly. Proofs later in the year let you true up. If employees submit everything in the last month, their final paycheques can shrink sharply, which is a bad surprise for everyone. Remind them ahead of time.

Depositing and reporting TDS

• Deposit the tax you deducted with the government by the due date each month. Check the current deposit deadlines, including the special rule for March.
• File quarterly TDS statements for salary using the prescribed form.
• Issue annual salary TDS certificates to employees after the year ends.
• Reconcile what you deducted with what shows in each employee's tax statement on the government portal.

Missing a deposit or filing usually attracts interest and late fees. It can also make the employee's credit look wrong, which brings you angry emails.

Step 7: Provident fund, ESI and professional tax in practice

If you are registered, these three are the recurring statutory deductions that startups most often find confusing.

Provident fund

• Employees and employer both contribute a percentage of a defined wage amount, subject to rules about wage ceilings and options.
• Contributions are deposited monthly, and a monthly return is filed through the EPFO employer portal.
• Each employee needs a UAN. New employees who have never worked before get one created; those with a previous job should reuse theirs.
• Keep the employer share and the administrative charges in your cost projections, not just the employee share.

ESI

• Applicable to eligible employees whose wages fall within the notified ceiling, and only if your establishment is covered.
• Both employee and employer contribute a percentage of wages, deposited monthly through the ESIC portal.
• Coverage is assessed per contribution period, so an employee who crosses the ceiling mid-period may continue in the scheme until the period ends. Check the current rules before making any change.

Professional tax

• Levied by certain states on employees' income, deducted by the employer and deposited to the state.
• Slabs differ by state, and some states have different rules for certain months or for women, senior employees or other groups.
• Registration, return frequency and due dates are state-specific.

Because every rule here has thresholds and exceptions, the safest approach is to let a payroll system apply them and to have an advisor check the setup once. Do not memorise the numbers, because they change.

Step 8: Disbursement, done safely

Computation is only half the job. Money has to leave your bank account correctly, on time and with an audit trail.

Choosing a payment method

• Bulk transfer file from net banking. Most business banks accept a file in a defined format. Payroll software generates it and you upload it.
• Direct integration or payout API. Some banks and software tools support one-click release after approval.
• Individual transfers. Fine for two people, painful for ten, and a source of typos.

A safe disbursement routine

1. Two-person rule: one person prepares, another approves.
2. Compare the bank file total with the payroll register total.
3. Check the first few and last few rows for format problems.
4. Release the file and keep the confirmation.
5. Track returned or failed payments the next business day and fix them immediately.
6. Mark payroll as paid only after the bank confirms.

Keep statutory money in mind

When you release net pay, you also owe the government the amounts you withheld and any employer contributions. Set aside those funds in the same cycle. A common startup problem is spending the withheld TDS and PF as working capital and then scrambling on the due date.

Pay on time, every time

Delayed salary damages trust faster than almost anything else. If cash is tight, tell the team early and give a date. Also check what your state law and your own offer letters say about the timing of wage payment, since the rules may set expectations around when salary must be paid.

Step 9: Payslips that people can actually read

A payslip is both a communication and a record. Employees use it for loans, visas, rent agreements and tax filing, so accuracy matters.

What a good payslip contains

• Company name and address
• Employee name, ID, designation, department and location
• Pay period and paid days
• Earnings by component, both full and actual for the month
• Deductions by component
• Net pay in figures, and often in words
• Bank account (masked) and payment date
• Year-to-date totals
• Leave balances, optionally

Some states or laws prescribe records and formats for wage slips and registers. Ask your advisor which apply to you.

Delivery and privacy

Publish payslips through a secure employee portal or password-protected files rather than a forwarded spreadsheet. Give each employee access only to their own record. Keep a history so anyone can download last year's payslips without asking HR.

Make queries easy

Add a short line to the payslip email: who to contact, and by when. Track queries in a simple log. Repeated questions about the same item usually point to a confusing structure or an unclear policy that you can fix once.

Step 10: The statutory filings calendar

Below is a generic calendar to help you plan. Due dates, forms and portals change, and some vary by state. Treat it as a planning skeleton and replace each line with the dates confirmed from official sources.

Build your own compliance tracker

Create a shared sheet or use your payroll tool's reminders with these columns:

• Obligation
• Portal
• Due date rule
• Owner
• Backup owner
• Status this month
• Challan or acknowledgement reference

Assign a backup owner. A due date that only one person knows about is a single point of failure.

Keep proof

Store challans, acknowledgements and returns in an organised folder by financial year. During funding due diligence, an acquisition or a labour inspection, well-organised proofs are worth more than any explanation you can give.

The first-month checklist

Use this as a working list. Tick each item, note the date and the owner.

Two to four weeks before the first payday

• [ ] Confirm legal entity, PAN and TAN
• [ ] Discuss with your advisor which of EPF, ESI, PT, LWF and shops act registrations apply
• [ ] Apply for applicable registrations and note application dates
• [ ] Open or confirm a current bank account with net banking access and approval limits
• [ ] Draft salary structure and leave policy
• [ ] Issue offer letters and appointment letters that match the structure
• [ ] Choose a payroll tool or process

One to two weeks before

• [ ] Collect and verify all employee master data
• [ ] Collect tax regime choices and declarations
• [ ] Collect previous employer details for mid-year joiners
• [ ] Set attendance and leave rules and communicate the cut-off date
• [ ] Set up statutory portal logins with named owners
• [ ] Run a test payroll for one or two dummy employees

Payroll week

• [ ] Freeze attendance and inputs on the cut-off date
• [ ] Run the draft payroll and review variances
• [ ] Get second-person approval
• [ ] Generate the bank file and match totals
• [ ] Release salary and save confirmation
• [ ] Publish payslips
• [ ] Set aside funds for statutory deposits

After payday

• [ ] Deposit TDS, PF, ESI, PT and others by their due dates
• [ ] File monthly returns where applicable
• [ ] Log employee queries and resolve them
• [ ] Reconcile the payroll register with the ledger
• [ ] Do a short retrospective: what was late, what was wrong, what to fix

Mistakes to avoid in your first payroll

1. Starting without TAN or with a wrong PAN

Without TAN you cannot properly deduct and deposit tax. A wrong PAN in an employee record leads to credit mismatches. Verify both before the first run.

2. Treating statutory registrations as "later" tasks

Registrations feel optional until an employee asks for a PF passbook or a notice arrives. Ask your advisor at the start and record the decision, even if the answer is "not yet applicable".

3. Building a structure that only works on a spreadsheet

If the structure needs a manual fix every month, it will break when you hire the fifteenth person. Prefer a few consistent components with formulas over many custom ones.

4. Skipping the cut-off

Accepting changes until the moment of payment turns payroll into a scramble. A published cut-off protects both HR and employees.

5. Ignoring state differences

Professional tax, labour welfare fund and shops act rules depend on where the employee works. Record the work location for every person, even remote staff.

6. Forgetting the previous employer's income

If a mid-year joiner's earlier salary is missing, your TDS calculation will understate their income. They may face a large tax bill later, and you may face a difficult conversation.

7. Paying first, computing later

Some founders transfer "roughly the right amount" and plan to fix it next month. Corrections then compound. Compute, review, approve and only then pay.

8. Mixing personal and company funds

Salary, statutory deposits and reimbursements should flow from the company account with a clear audit trail. Paying from a personal account complicates books, tax and later audits.

9. One person, no backup

If only one person knows the process, a sick day or resignation can stop payroll. Document the steps and train a backup.

10. No records

Keep payroll registers, challans, returns, declarations and approvals. If you did it but cannot show it, an auditor may treat it as not done.

Manual, spreadsheet or software: choosing your approach

Most startups begin with a spreadsheet. That is fine for the first few employees if you are careful. Trouble begins when rules multiply: proration, statutory ceilings, tax projection, reimbursements and reporting.

When evaluating any tool, ask these questions:

• Does it handle attendance and leave integration so that paid days flow into payroll automatically?
• Can it configure provident fund, ESI, professional tax and labour welfare fund by state?
• Does it project and compute TDS with regime choice and declaration handling?
• Does it generate bank files, payslips and statutory reports?
• Does it provide an approval workflow and an audit log?
• Can employees access their own payslips and submit declarations?
• How does it handle changes when rules are updated?

The benefit of a connected system is that the same attendance record that employees see is the one payroll uses. That removes a whole category of disputes.

What good looks like after three months

By the third payroll, you should notice these signs of a healthy process.

• Inputs arrive before the cut-off without chasing.
• The variance report contains only explainable changes.
• Statutory deposits are made a day or two before the due dates.
• Employees rarely ask about the same thing twice.
• A backup person can run the process with your checklist.
• Your advisor spends time on judgement, not data cleaning.

If you are not there yet, that is normal. Pick the one weakest step, fix it and move on to the next.

Frequently asked questions

1. When should a startup run its first payroll in India?

Once you have an employee on your rolls, salary becomes due according to the terms in the appointment letter and applicable law. Plan the registrations, structure and data collection before the first payday, ideally a few weeks ahead, so that the first cycle is not the first time you learn the process.

2. Do I need a TAN if I have only one or two employees?

If you deduct tax on salary, you need a TAN to deposit and report it. Whether tax is actually deducted depends on each employee's estimated taxable income and chosen regime. Confirm with your advisor, and get the TAN in place before the first salary in any case.

3. Is provident fund compulsory for a small startup?

Applicability depends on headcount and coverage rules, and some establishments can opt in voluntarily. Check the current EPFO rules or ask your advisor. Even if it is not mandatory yet, decide deliberately, because it affects hiring conversations and future compliance.

4. What if my startup operates from a co-working space or from home?

Registrations such as shops and establishments and professional tax generally depend on where the business operates and where employees work. A co-working address or a home address can still be a place of business for these purposes. Ask your advisor how your local authority treats it.

5. How do I handle employees who joined mid-year for TDS?

Collect their previous employer's income and tax deduction details for the current financial year, and include them in your projection. This avoids under-deduction and a large tax bill later.

6. Can I change the salary structure after the first payroll?

Yes, but do it deliberately. Communicate changes in writing, apply them from a clear effective date and make sure the change is consistent with what employees agreed to. Avoid ad hoc changes for individuals unless the reason is documented.

7. What records should I keep from the first payroll?

Keep the payroll register, attendance and leave records, approvals, bank confirmation, payslips, challans and acknowledgements for every deposit and return, employee declarations and proofs, and the registration certificates. Ask your advisor how long each category should be retained.

8. Should I use a spreadsheet or payroll software?

A spreadsheet can work for a handful of people if the structure is simple and someone reviews it carefully. As soon as you add statutory deductions across states, tax projections and frequent joiners and leavers, software reduces both effort and errors.

Conclusion

Your first payroll for a startup in India does not need to be perfect, but it does need to be deliberate. Sort out your registrations with an advisor, collect clean employee data, keep the salary structure simple, fix an attendance cut-off, compute in a repeatable order, handle TDS carefully, pay through a checked bank file, publish clear payslips and keep a filing calendar with owners and backups.

Do that once and the second month is easier. Do it consistently and payroll becomes a quiet, reliable background process rather than a monthly fire drill, which frees you to spend time on the product and the customers.

If you would like to see how attendance, leave, payroll, TDS and payslips can sit in one place for an Indian team, you are welcome to try CozyHR and explore whether it suits the way your startup works. Whichever route you choose, verify current statutory rules with official sources or a qualified professional before you finalise your setup.