Professional tax rarely gets attention in a payroll review. It is a couple of hundred rupees a month, it is capped by the Constitution at ₹2,500 a year per employee, and next to provident fund or income tax it looks like rounding. That is precisely why it goes wrong. Nobody checks a deduction that small — until a state notice arrives, or an employee who moved cities notices they are being taxed by a state they have never worked in.
The underlying awkwardness is structural. Professional tax is not one tax. It is a separate levy imposed by individual states and union territories under Article 276 of the Constitution, each with its own statute, its own slabs, its own return calendar and its own registration process. A company operating in four states is administering four different taxes that happen to share a name.
Who levies it, and who is liable
Article 276(2) allows states to tax professions, trades, callings and employments, and caps the total at ₹2,500 per person per year. That ceiling has not moved in decades, which is why professional tax stays small even as salaries rise.
Two distinct liabilities follow from the same statute, and conflating them is a common source of confusion:
- Professional tax on employees (PTRC). The employer deducts it from salary and deposits it. The employee is the taxpayer; the employer is the collection agent.
- Professional tax on the entity (PTEC). The business itself pays an annual amount for the privilege of carrying on its trade in that state. This has nothing to do with payroll and is often missed by companies that have registered only for PTRC.
Everything below concerns the first. If you have employees in a state that levies professional tax and you have not registered for PTRC there, deducting correctly is not enough — you have no way to deposit it.
The rule that causes the most errors: which state applies
The state that applies is determined by where the employee works, not where the company is headquartered, not where payroll is processed, and not where the employee is from.
This sounds obvious and is broken constantly, because most payroll systems hold exactly one state — the company's — and apply it to everyone. A Bengaluru company with a Chennai branch and a Pune site is liable under three separate professional tax regimes, at three different sets of slabs, on three different filing calendars. Running all three on the head-office state means simultaneously under-collecting in one state and over-deducting from employees in another.
Remote and hybrid work has made this materially harder. An employee hired to a Mumbai office who now works permanently from Indore is, in substance, working in Madhya Pradesh. Most companies have not revisited this, and the position is genuinely unsettled in places — but "we never thought about it" is a weaker answer than "we applied the state of the assigned work location and documented why".
Practically, this means the state has to be a property of the employee's work location and it has to flow into payroll automatically. In AttendancePay, professional tax resolves from the employee's work state, falling back to the state on their assigned branch, so a multi-branch company gets the right levy per person without payroll maintaining a spreadsheet of exceptions. If you are evaluating any payroll product for multi-state operations, this is a specific thing to test rather than assume.
Slabs change, and they change by notification
Every levying state publishes a slab schedule: bands of monthly salary, each with a fixed rupee amount. Maharashtra, as an illustration of the shape, exempts salaries up to ₹7,500, charges ₹175 between ₹7,501 and ₹10,000, and ₹200 above that — with a higher amount in one month of the year, which we will come to.
Deliberately, this article does not print a table of every state's slabs. Slabs move by state notification, often mid-year, and a table published once is wrong within a budget cycle or two. Karnataka, for example, raised its exemption threshold substantially in 2023, and payroll systems still carrying the older schedule quietly over-deduct from every employee in the band that became exempt. If your payroll software has a professional tax configuration, check when it was last reviewed against each state's current notification. A stale slab table is invisible: it produces a plausible number every month and nobody notices until an employee or an auditor does the arithmetic.
The mechanics that do not change, and which are worth understanding properly, are below.
Five things that go wrong in real payroll runs
1. The February instalment is missed
Several states — Maharashtra and Madhya Pradesh among them — do not divide the annual liability into twelve equal parts. They charge a standard amount for eleven months and a higher amount in the final month of the financial year, so the total reaches the annual figure. Maharashtra's ₹200 becomes ₹300 in February; the year totals ₹2,500.
Payroll that applies the same monthly slab twelve times under-collects, and the shortfall is the employer's problem to make good. Equally, the February uplift must not apply to employees who fall in an exempt (zero) slab — charging ₹300 to someone who owes nothing all year is a straightforward over-deduction, and it is an easy bug to write.
2. The gross used is the contractual one, not the earned one
Professional tax is levied on salary actually earned in the month. An employee on a contractual gross of ₹26,000 who lost eight days to unpaid absence did not earn ₹26,000, and in several states that drops them into a lower slab — occasionally into the exempt band entirely.
Most payroll systems apply the slab to contractual gross because it is the simpler number to reach for. It is also the wrong one. AttendancePay makes this an explicit per-company setting rather than a silent default, precisely because switching an existing company from one basis to the other changes historical comparability, and that should be a decision someone makes rather than an upgrade that happens to them.
3. Exemptions are ignored
Most states exempt specific categories — commonly employees with disabilities and, in some states, parents or guardians of a child with a disability. Several states additionally exempt senior citizens or apply a higher threshold for women. These are not automatic: the employee has to be flagged, usually against documentation held on file. An exempt employee who is deducted anyway has a legitimate grievance and a paper trail proving it.
4. Mid-month joiners and leavers are handled inconsistently
Professional tax is a fixed monthly amount, not a rate, so it does not pro-rate naturally. States differ on whether a partial month attracts the full amount. The failure mode is not usually picking the wrong answer — it is picking different answers in different months because nobody wrote the rule down. Decide the treatment once, document it, and make sure the system applies it without human judgement.
5. Deduction is correct but the return is late
Filing frequency varies by state and often by the size of the liability — monthly for larger employers, annually for smaller ones, with the threshold set per state. Because the amounts are trivial, professional tax returns are the ones that slip. The interest and penalty are usually larger than the tax. A compliance calendar that carries every state you operate in, rather than every tax you remember, is the cheapest fix available; our payroll compliance calendar is a starting point you can adapt.
What to automate, and what to keep human
Professional tax is a good candidate for full automation because every input is structured: the employee's work state, their earned gross for the month, their exemption status, and the calendar month. There is no judgement in the calculation itself. Once state resolution and the slab schedule are correct, the deduction should never need a manual touch — and it should appear on the payslip as a named line so employees can see what was taken and why.
What stays human is maintenance. Someone has to own the question "have any of our states changed their slabs?" on a recurring basis. No payroll product answers that for you, whatever the marketing implies; the honest position is that the software applies the schedule it has been given, and keeping that schedule current is a shared responsibility between the vendor and the company.
If you want to sanity-check what a specific salary should produce across statutory deductions, our salary calculator and CTC calculator break the components apart, and the PF and ESI calculators cover the two deductions that usually sit alongside professional tax on the same payslip.
A short checklist
- List every state you have employees working in — not offices, employees.
- Confirm you hold PTRC registration in each, and PTEC where the entity is liable.
- Verify each employee's work state is recorded on their record, not inherited from head office.
- Check when your slab configuration was last reviewed against current state notifications.
- Confirm the February (or state-equivalent) final instalment is applied, and only to non-exempt employees.
- Decide and document the basis — earned or contractual gross — and the mid-month joiner rule.
- Put every state's return due date on one calendar with a named owner.
None of this is difficult. It is simply spread across more statutes than a single payroll team naturally tracks, which is why it drifts. Getting it structurally right once is considerably cheaper than reconstructing three years of deductions when a state asks.
