Professional tax as a state payroll deduction

Professional tax (PT) is a state-level levy where a state charges it on professions, trades, or employment as that state’s law provides. In payroll it appears as a configured deduction on the payslip when you have decided it applies to that employee for that period. It is not a single all-India slab, not a central Income Tax line, and not legal advice. This article does not publish a multi-state slab table. Pending SME review; remains a draft.

Liability, who is an employer for PT, periodicity (monthly or otherwise), exemptions, and current amounts differ by state and can change. Verify on the commercial-tax, profession-tax, or equivalent authority materials for the state that actually applies — not on a national blog grid. Dayzen payroll can calculate PT as a configured component; it does not file state PT returns or pay the state. Calculation versus filing stays on the payroll calculation versus filing guide. What PT is among other statutory calculation components, without rates, is on India statutory payroll calculations.

Location assignment is the first payroll fact

Before a slab conversation, know which state’s rule you are even looking up. That usually follows where the employee is assigned for this purpose: work location, establishment, or another mapping your reviewed policy uses. The mapping must live on the employee master, with history, not in a payroll admin’s memory.

A person on a Maharashtra template who sits in a different state on the attendance roster will dispute the PT line — or never have one when the other state expected it. Fix location as an effective-dated assignment, then configure. Do not “just add a deduction” because a consultant emailed a chart.

Multi-state employers need a rule for people who travel, work remotely, or transfer mid-month. This page will not invent that rule. Write whether PT follows the location as of a freeze date, a majority of days, or the establishment that holds the employment. Then keep attendance and the master from telling two stories.

Entity (which company employs the person) and location (which state rule) can both matter. Do not collapse them. Two companies in one city can still have two PT registrations and two filing owners outside the HRMS.

PT as a deduction line, not a filing receipt

On the payslip, PT should be a named deduction when it was calculated. Employees should not have to reverse-engineer it from net. The line means payroll computed the configured amount for this period. It does not mean the state return was filed or the state was paid.

If a month has no PT under your configuration (not due, not applicable, or a periodicity that skips this month), either omit the line or print zero with a label your SOP explains. Random appearance and disappearance of the heading produces tickets.

YTD PT, if you print year-to-date, should use the same year your payroll uses for that component. Do not mix a financial year and a calendar year silently. YTD is still not the state’s annual statement.

Configuration without a pasted grid

In Dayzen payroll, PT is a statutory calculation you configure. Configuration should come from the state materials and your consultant for each location you operate — copied into the system by an accountable owner, with a dated log. Do not paste a seven-state table from a news article into the template. Those tables go stale, omit exemptions, and mix employer classes.

What to capture in the SOP instead of a fake national chart:

• Which locations are in scope, and which state authority is the lookup source for each.
• Which employee classes you treat as in or out of PT after review (do not invent a nationwide exemption list here).
• Which earning base the configured calculation reads (as your reviewed mapping, not as a blog definition of “salary”).
• Periodicity and how a given pay month maps to a PT period.
• Who files and who remits — names outside the HRMS if that is your model.

When a state revises its schedule, treat it like any other statutory configuration change: effective date, who verified the official text, test on a sample employee, then freeze. Do not wait for an employee ticket to discover the old amount still calculating.

Joiners, leavers, unpaid days, and PT

Whether a mid-month joiner or leaver attracts a full period’s PT, a reduced amount, or none is a function of the state rule and your reviewed method — not a fact this page will standardise. Write the method per location. Do not assume unpaid days automatically cancel PT, or that PT is independent of earnings, without checking the configured rule and the official text.

If LOP reduced the earning base that PT reads, the PT amount may change. That is a consequence of configuration. It is not a second LOP. Keep the LOP rupee method on its own page; here, only notice that PT is downstream of earnings if you built it that way.

Transfers: a location change mid-period needs an effective date and a decision which state’s calculation applies to which days or which month. Silent dual PT or a gap month is a typical bug when HR updates the city in chat and payroll never sees it.

Employees who work from a different state than the office

Remote and hybrid patterns make “office address on the letterhead” a poor proxy. Decide what location assignment means for PT and say it in the employment or payroll SOP. If you do not know, do not guess a slab; escalate to SME review with the actual working pattern.

Do not run one PT configuration “for all India” because most of headcount sits in one city. The minority locations are where assessments and employee disputes start.

What not to tell employees

Do not say PT is “like TDS but smaller.” Different sovereign, different portal, different owner. Do not say Dayzen “paid your professional tax” because the line printed. Do not quote another company’s amount as the law for your state.

If an employee claims exemption or a special category, take documents through the process you reviewed. Payroll should store the outcome (apply PT / do not apply) as a dated flag, not as a chat exception that expires when the admin changes.

Month-end: calculate here, file there

PT calculation belongs in the pay run with other deductions after earnings and LOP are known. PT filing and payment belong on the state calendar the finance or consultant owns. Mixing them produces the same failure as mixing TDS withholding with the income-tax return: the PDF looks complete and the portal is late.

Reports from payroll should give the filing owner identity, location, period, and calculated PT. That is a handoff file, not an auto-submit. Dayzen does not claim state-portal filing.

SME-gated items left open

Current slabs by state, enrolment or registration duties, due dates, return forms, and whether a particular remote pattern is liable are not published here. Official state PT or commercial-tax materials, plus counsel, are required. Labour-code debates that some blogs tie to PT are not settled on this page.

---

PT is state-wise. Assign location, verify that state’s authority, configure the deduction, calculate it in the pay run, and let a named owner file outside the HRMS. No multi-state table belongs in this article. Dayzen calculates PT as configured; it does not file state returns. This article remains a draft pending SME review.

If you add a new office city, add a PT lookup and a filing owner before the first pay run in that city. Retrofitting PT after six months of payslips is an adjustment project, not a checkbox, and employees will not thank you for a sudden YTD catch-up they never saw coming.

A walkthrough without a slab table

Imagine three people in one pay run, as an operating story, not as law. Person A is assigned to a state that levies PT and is in a class your reviewed configuration treats as liable: payroll calculates the configured deduction. Person B is assigned to a state that does not levy PT, or to a class your review treats as out of scope: no PT line, and the SOP says why so the ticket “why did I not get PT” has an answer. Person C transferred location effective mid-month: payroll uses the written transfer rule, not a blended guess. None of those three sentences requires publishing amounts. The amounts live in configuration sourced from the state authority for A’s state, verified on a dated log.

When Person A disputes the rupee, the first checks are identity, location assignment as of freeze, and whether the earning base this month matched what the configuration expected (for example after unpaid days). Only then do you reopen whether the configured schedule still matches the official text. Starting with a screenshot of another company’s slip skips those checks and usually copies the wrong state.

Registration, enrolment, or establishment numbers — if your state process uses them — belong with the filing owner. They are not payslip decoration. Printing a registration number that is stale does more harm than printing none. Keep the HRMS responsible for employee identity, location, and calculated PT; keep the portal credentials and return calendar off this document.

Off-cycle bonuses or an extra run in the same month should follow the same configuration, not a one-off typed deduction, unless you have a written exception. Typed PT is how YTD and the handoff file diverge. If you must correct a prior month, use a named adjustment path so the filing owner can see which period the rupees belong to.