A plain-English guide to Indian payroll compliance in 2026: PF, ESI, TDS and professional tax rates and deadlines, what the new Labour Codes changed in April 2026, and how payroll software handles it for you.
Paying your team is the easy part. The hard part of Indian payroll is the statutory compliance wrapped around it - PF, ESI, TDS and professional tax - each with its own rate, deadline and return. Get it wrong and the penalties are real. And in 2026 the rules shifted, because the four Labour Codes finally came into force. Here is the plain-English version.
The four Labour Codes became operational in April 2026, the biggest change to Indian payroll in years. The headline for employers: under the Code on Wages, 'wages' must now be at least 50% of total CTC (basic pay plus dearness allowance). Because PF, ESI and gratuity are calculated on this base, redrawing salary structures changes contributions and take-home across the board. Other changes include a wider ESI footprint (coverage extended across all of India), revised contribution bases, and Form 16 being replaced by Form 130. Penalties for non-compliance also rose sharply.
If your salary structures still treat basic pay as a small slice of CTC, they likely need restructuring - and your payroll software should already reflect the new definition.
Both employee and employer contribute 12% of basic + DA each. It applies to establishments with 20+ employees (and is mandatory for employees earning up to the wage ceiling). PF dues are payable by the 15th of the following month.
ESI applies to employees earning up to Rs.21,000/month. The employee contributes 0.75% and the employer 3.25% of wages, payable by the 15th of the following month. Under the new codes, ESI coverage now extends across all areas of India.
You must deduct tax at source on salaries based on each employee's estimated annual income. In practice: estimate annual income, apply the (default) new-regime slabs, allow the standard deduction, apply the Section 87A rebate where eligible, add 4% cess, and divide by 12 for the monthly deduction. TDS is deposited monthly and reported in quarterly returns.
Professional tax is a state-level tax (so rates and rules vary by state, and some states do not levy it at all), typically a small monthly amount deducted from salary and deposited with the state. Because it is state-specific, this is one of the easiest things to get wrong manually.
Each deduction has its own rate, threshold, deadline and return, and they interact (the wage definition feeds PF and ESI; the regime choice feeds TDS). Doing this in a spreadsheet across a growing team is how mistakes - and penalties - happen. India-built payroll software computes every deduction, generates the challans and returns, and files on time, while keeping up with rule changes like the 2026 Labour Codes.
If you are choosing a tool, our guide to the best payroll & HR software for small business in India compares RazorpayX Payroll, Keka, greytHR, Zoho People, factoHR and Darwinbox by business size, and you can browse every option in the HR & Recruiting category.
Statutory rates, thresholds and deadlines change, and the Labour Code rollout has transition details. Confirm current rules with an official source or your CA before running payroll.
Turn this research into a workflow with apps, stages, caveats, and next actions.
Start with the product itself: a place to write and ship code, host it reliably, and catch errors in production, because nothing else matters until customers can actually use what you built. Next, get the team coordinated with project management and a shared knowledge base so work and decisions are not lost in chat. Then put customer acquisition on a real CRM so leads, demos, and deals are tracked rather than living in inboxes. Add billing and accounting once you have paying users, choosing payment rails that fit whether you sell to India, abroad, or both, and keep GST-clean books from day one. Finish with customer support, product analytics, and access security so you can keep users happy, see what they actually do, and not get breached. Do not buy enterprise sales, analytics, and security suites before you have product-market signal; sequence around shipping and getting your first paying customers.
View stack
Start by choosing the right no-code platform for what you are building, because a customer-facing web app, a mobile app, and an internal portal each suit different tools. Next, model your data cleanly in a database or spreadsheet backend, since a messy data model is the most common reason no-code projects collapse later. Then build the interface and logic so users have real screens and workflows, not just a database. Add payments, forms, and automations to connect your app to the outside world and remove manual work. Finish by launching, securing team access, and measuring usage so you know the app works and is safe. Do not expect no-code to scale infinitely; it is excellent for validating and running real workflows, but be honest about its ceilings and plan to move to custom code if you outgrow it.
View stack
Start by choosing a website builder that matches your skill and needs, because the builder decides how fast you launch and what you can do later. Sort your domain and hosting next, remembering that most builders bundle hosting while self-hosted WordPress needs its own, so you do not pay twice. Then design and write the site so it looks credible and explains clearly what you offer, since a confusing site loses visitors in seconds. Add lead capture, booking, and payment tools so the site actually does something, whether that is collecting enquiries, taking appointments, or selling. Finish by getting found and measuring, with basic SEO, a Google presence, and analytics so you know what is working. Do not over-build a complex site before you have visitors; launch a clear, fast site and improve it with real data.
View stack
Describe your actual business goal and FindThatSoftware will map the apps, trade-offs, setup stages, and buying caveats.
Build a pipeline