Professional Tax Compliance: A State-Wise Employer Guide

Professional Tax Compliance: A State-Wise Employer Guide

Most Indian SMBs meet professional tax compliance the hard way. You run payroll cleanly for two years out of a single office, everything ticks along, and then you hire your first salesperson in another state — or let a developer relocate home and work remotely — and suddenly a deduction line that was always the same for everyone is not the same for everyone anymore. Somebody asks why their take-home dropped by a few rupees. Somebody else asks why theirs didn't. And your payroll person discovers that the state you just hired into wants a registration certificate you don't have.

Professional tax, usually shortened to PT, is a small-value, high-irritation levy. The rupee amounts are modest — the Constitution caps what any state can charge a single person in a year — but the administrative surface area is large, because every state that levies it writes its own slabs, its own registration process, its own return formats and its own due dates. There is no central portal, no single challan, no unified return. If you employ people in six states that levy PT, you have six separate compliance tracks.

This guide is written for HR managers, founders and payroll teams who need to get PT right without becoming tax lawyers. It covers what PT is and where states get the power to charge it, the difference between the employer's certificate and the employee's certificate, which states commonly levy it and which commonly don't, how to configure PT correctly in payroll software (this is where most errors are actually created), the mistakes that show up again and again in audits, and what to do when you find out you've been getting it wrong. A standing caveat runs through the whole piece: states revise slabs, thresholds, exemptions and filing calendars, so treat everything here as structural guidance and confirm current numbers on the relevant state commercial tax or PT department portal before you configure anything.

What Professional Tax Actually Is

Professional tax is a tax on professions, trades, callings and employments. Despite the name, it has nothing to do with being a "professional" in the colloquial sense. If you earn a living in a state that levies it — as a salaried employee, a self-employed consultant, a partner in a firm, a director drawing remuneration, a shopkeeper or a freelancer — you are potentially within its scope.

It is levied by state governments, and in some states collected by local bodies such as municipal corporations or panchayats. It is not an income tax in the central sense, it is not linked to the Income Tax Act's computation machinery, and it is not administered by the Income Tax Department. It sits with state commercial tax departments or their equivalents.

The amounts are deliberately small. PT is a flat or slab-based charge, not a percentage of income that scales indefinitely. Two people earning very different salaries in the same state may pay the same PT if they fall in the same top slab. That flatness is what makes it administratively simple in principle and surprisingly error-prone in practice — because the logic is "which slab does this person's monthly earnings fall into, in this state, this month," and every one of those variables can move.

Why It Exists at All

The design intent is straightforward: give states a small, broad-based revenue stream tied to economic activity within their borders. In several states, PT collections are earmarked or associated with education and local body funding. For employers the intent doesn't matter much; the obligation does.

The Constitutional Basis: Article 276

The power to levy PT comes from Article 276 of the Constitution, which allows state legislatures (and, through them, municipalities and local boards) to impose taxes on professions, trades, callings and employments. Crucially, Article 276 also makes clear that such a tax is not invalid merely because it looks like a tax on income — which is a central subject. That carve-out is what lets PT coexist with income tax without a constitutional conflict.

The article also sets a ceiling on the total amount that can be charged to any one person in respect of any one state in a financial year. That ceiling is why PT never becomes a large number, and why the top slab in every state converges toward a similar annual figure. We are deliberately not quoting the ceiling amount here; check the current constitutional limit and the state's own schedule, because the figure has been revised historically and proposals to revise it surface periodically.

Two practical consequences follow from the ceiling:

• Your maximum annual exposure per employee per state is bounded. This is useful when you are estimating a past-period shortfall — the arithmetic has a hard upper bound.
• Some states structure the year unevenly to reach the ceiling. If the annual ceiling doesn't divide neatly into twelve equal monthly instalments, a state may specify a different (usually higher) deduction in one month — commonly February — so the twelve months add up correctly. This is the single most-missed rule in PT configuration, and we come back to it later.

PT and Section 16 of the Income Tax Act

There is one interaction with income tax worth knowing. Professional tax actually paid by a salaried employee is allowed as a deduction from salary income under the old tax regime. Whether that benefit is available under the regime an employee has opted into is a separate question that has moved with successive Finance Acts, so confirm the current position with your tax advisor rather than assuming it carries across regimes.

What this means operationally: PT paid must be reported correctly in the salary computation and Form 16 workings, which is another reason the payroll system's PT figures need to be right and traceable, not approximately right.

Who Is Liable: PTRC vs PTEC

This is the distinction that causes the most confusion in early-stage companies, so it is worth being precise. In most PT states there are two separate registrations, and an employer typically needs both.

The employer's registration — commonly called PTRC (Professional Tax Registration Certificate). This is your authority and obligation to deduct PT from employees' salaries and remit it to the state. You register as an employer, you deduct from each eligible employee each month, you deposit the aggregate, and you file the return. The employee is the taxpayer; you are the collection agent.

The entity's own enrolment — commonly called PTEC (Professional Tax Enrolment Certificate). This is the tax the business entity itself pays on its own account for carrying on a trade or profession in the state. A private limited company, LLP, partnership firm or proprietorship is typically liable in its own right, separate from anything it deducts for employees. Directors and partners may also have individual enrolment obligations in some states.

Naming varies. Some states use different acronyms or a single combined certificate. Some use "registration" for both and distinguish by certificate type. Don't assume the Maharashtra terminology applies verbatim elsewhere — check the state's own forms.

A Simple Way to Remember It

If money is coming out of somebody's salary, that's the employer registration track. If money is going out because your company exists and operates in that state, that's the enrolment track. You can be fully compliant on one and completely delinquent on the other, and many SMBs are.

Directors, Partners and Proprietors

In several states, directors drawing remuneration, working partners and proprietors have their own PT liability — sometimes as employees (where they draw a salary) and sometimes under enrolment. Founders frequently overlook themselves. If you drew director's remuneration in a PT state all year and never paid PT on it, that's an open item. Verify the specific state's treatment, because some states treat directors as employees only where an employer-employee relationship genuinely exists.

Which States Levy Professional Tax — and Which Don't

PT is not a national levy. Roughly half of India's states and union territories charge it; the rest do not. Getting this map wrong in either direction costs you: deducting where no levy exists means you have taken money from employees you had no authority to take, and not deducting where it does exist means you have a liability with interest running.

States and union territories that commonly levy professional tax include Maharashtra, Karnataka, West Bengal, Tamil Nadu, Andhra Pradesh, Telangana, Gujarat, Madhya Pradesh, Kerala, Assam, Odisha, Bihar, Jharkhand, Meghalaya, Tripura, Sikkim, Nagaland, Manipur, Mizoram and Puducherry.

States and union territories that commonly do not levy it include Delhi, Haryana, Uttar Pradesh, Rajasthan, Himachal Pradesh, Uttarakhand, Chandigarh, Goa and Andaman & Nicobar Islands. Punjab is a special case worth noting separately: it levies a development tax on persons in employment and professions which functions similarly to PT in payroll terms even though it is not named professional tax.

Treat both lists as "commonly," not "permanently." States do introduce the levy, repeal it, or restructure it, and local-body-administered variants exist in some places. Before you switch PT on or off for a location, confirm on the state's own commercial tax or finance department portal.

The Local Body Wrinkle

In a few states PT is administered at the municipal or panchayat level rather than purely at state level, which means registration, payment channels and even applicability can vary by city or local authority within the same state. Kerala is the commonly cited example of local-body administration. If you have an office in a state with local-body collection, confirm with the specific municipality, not just the state department.

How PT Slabs Work and Why They Differ

Every PT state publishes a schedule of slabs. The structure is almost always the same: bands of monthly salary or wages, each mapped to a fixed rupee amount of tax. Below the lowest threshold, nil. Above the top threshold, a flat maximum.

What differs between states is everything else — the number of bands, where the thresholds sit, the rupee amount per band, whether the measure is monthly salary or annual income, whether there is a separate schedule for non-salaried persons, and what counts as "salary" for the purpose of the test.

Here is an illustrative structure only, with placeholder values, to show the shape. These are not real slabs for any state — do not configure from this table.

Notice what the shape implies. PT is a step function, not a smooth one. An employee who crosses a threshold because of one month's incentive payout can jump a slab for that month alone, and drop back the next month. Whether that is correct depends on how the state defines the base — which is the next question.

What Counts as "Salary" for the Slab Test

States differ on this and the differences matter. Common variations include whether the test uses gross salary or a narrower definition, whether variable pay, bonus, overtime, arrears and reimbursements are included, and whether employer contributions to retirement funds are counted.

Do not assume your Karnataka logic works in West Bengal. Read each state's definition, write it down in your payroll configuration notes, and record which definition you applied. Your future self, or your auditor, will want that note.

Monthly Schedules vs Annual Schedules

Most states run a monthly slab test. Some express the schedule annually and expect the employer to divide across the year, and some run annual payment cycles for smaller employers. Where the schedule is annual, mid-year salary changes create genuine ambiguity about which band applies — resolve it by reference to the state's rules, and apply the same treatment consistently rather than case by case.

The Deduction and Remittance Cycle

The mechanics are simple in outline and fiddly in detail.

1. Determine applicability. Is there a PT levy at the employee's work location state? If not, stop — no deduction.
2. Determine the base. Compute the state-defined salary measure for that employee for that month.
3. Map to slab. Find the band and the corresponding amount.
4. Deduct. Show it as a distinct line on the payslip, not merged into "other deductions."
5. Aggregate by state and registration. Your remittance is per registration certificate, per state.
6. Deposit within the state's due window. Monthly for most employers in most states; some states allow quarterly or annual deposit below an employee-count or liability threshold.
7. File the return. Format, periodicity and portal are state-specific.
8. Archive proof. Challan, acknowledgement, and the employee-level register that ties the total back to individuals.

Deposit frequency commonly depends on your size. A state may require monthly deposit above a certain number of employees or a certain annual liability, and permit quarterly or annual deposit below it. That threshold can change, and crossing it as you grow is a silent trigger — nobody sends you a letter saying your filing frequency just changed.

Due Dates

We are deliberately not listing due dates. They vary by state, by return type, by employer category, and they get extended. What we will say is structural:

• Build a per-state calendar as a first-class artifact, not a note in someone's head.
• Set internal deadlines several days ahead of statutory ones.
• Re-verify the calendar at the start of each financial year, because states revise filing schedules more often than they revise slabs.
• Keep the calendar owner named. Unowned calendars rot.

Configuring PT in Payroll Software: The Part That Actually Matters

Almost every PT error is a configuration error, not a knowledge error. Someone on the team knows the rules; the system doesn't implement them. Here is what a correct configuration needs to handle.

1. State Mapping by Work Location, Not Residence

This is the foundational rule and the most commonly broken one. PT applicability follows the state in which the employment is exercised — the work location — not the employee's home state, not their permanent address in the HRIS, and not the state where your registered office sits.

In your payroll master, PT state must be a field on the employment record, derived from the assigned work location or branch, not pulled from the personal address block. If your system derives PT from employee.address.state, you have a latent bug that will fire the moment someone from Bengaluru moves to Delhi without changing jobs.

Configuration rule: work location → PT state → PT registration certificate → slab schedule. Four links, each explicit, each auditable.

2. Mid-Month Joiners and Leavers

Most states treat PT as a monthly charge triggered by being in employment during the month, without pro-rating. An employee who joins on the 25th usually attracts the full month's PT, and one who leaves on the 3rd usually does too. But "usually" is doing work in that sentence — some states and some interpretations differ, and the base for the slab test in a partial month may be the actual earnings or the notional full-month salary.

The practical failure here is the salary-based slab test. If a joiner earns only a few days' pay, their actual earnings may fall into a lower slab or below the threshold entirely, even though their contracted monthly salary sits in the top band. Decide — by reference to the state rule — whether your test uses actual earnings for the month or contracted monthly salary, configure it explicitly, and document the choice.

3. Loss of Pay and Zero-Pay Months

Similar logic. An employee on extended unpaid leave may have low or zero earnings in a month. Is PT still due?

• If the state tests on actual salary paid, heavy LOP can drop someone into a lower slab or below the threshold.
• If the state tests on entitlement or contracted salary, LOP doesn't change the slab.
• If there is no salary payment at all in a month, there is usually nothing to deduct from — but the correct treatment (skip, or carry forward, or deduct from the next payment) varies.

Configure the LOP rule per state, and make sure your system doesn't silently produce a negative net pay by forcing a PT deduction against a zero-pay run.

4. Arrears, Increments and Retrospective Revisions

When you pay arrears in month N for months N-3 through N-1, do those arrears push the employee into a higher slab for month N?

Two defensible approaches exist: charge the slab based on the month's total actual payment including arrears, or attribute arrears back to the months they relate to and re-test each. States differ, and some are silent. Whatever you pick, pick one and apply it consistently — an auditor is far more forgiving of a documented consistent method than of ad-hoc treatment that varies by employee.

Illustrative example. Suppose an employee's normal monthly salary is ₹60,000 (illustrative) and in September they also receive ₹45,000 (illustrative) of arrears for prior months. Their September payment is ₹105,000. If your state tests on actual monthly payment, their September PT is computed on ₹105,000 and may land in a higher band. If your state attributes arrears to source months, September stays at ₹60,000 and the prior months get re-tested. Different answers, both arguable — so the configuration note matters more than the choice.

5. Remote Workers in a Different State

This is the live issue for most Indian SMBs right now, and it has no tidy universal answer.

An employee hired to your Bengaluru office who now works permanently from Jaipur raises a real question: is the employment exercised in Karnataka or Rajasthan? The answer affects whether PT applies at all, since one of those states commonly levies it and the other commonly does not.

The pragmatic framework most employers use:

• Where is the employee actually rendering services? That is the primary question under the "employment exercised" logic.
• Do you have an establishment in that state? If you have a registered place of business there, the case for that state's PT is stronger.
• What does the employment contract say the work location is? Not determinative, but it's evidence, and inconsistency between contract and practice is what gets questioned.
• Is the arrangement permanent or temporary? A three-week trip home is not a change of work location. A permanent relocation with an updated contract probably is.

Because the boundaries are genuinely unsettled, take advice for material populations, document the position you adopt, apply it uniformly, and revisit it annually. What you must not do is let it happen by accident — where remote employees end up in whichever state their HRIS address field happens to say.

6. Multi-State Branches and Multiple Registrations

If you employ people in five PT states, you generally need registration in each, separate deposits against each certificate, and separate returns. Your payroll system must therefore:

• Hold a registration certificate number per state entity.
• Tag every employee's PT deduction to exactly one certificate.
• Produce a per-certificate remittance summary that reconciles to the payroll register.
• Keep per-state historical slab versions so you can re-run a prior period correctly after a rate change.

That last point is underrated. If Karnataka revises slabs effective from a certain month and your system only stores the current slab table, you can never reproduce last year's calculation. Version your slab tables with effective-from and effective-to dates.

7. The February (or Other) Higher-Deduction Month

Where a state's annual total doesn't divide evenly into twelve, the schedule may specify a larger deduction in one designated month. Systems that hard-code "same amount every month" get this wrong, and the error is invisible for eleven months.

Configure the annual schedule, not a monthly constant. Then reconcile: for each employee in each state, does the sum of twelve months equal the state's prescribed annual total for their slab? If not, investigate before year-end, not after.

Common Professional Tax Errors

These are the ones that recur. Read this as a self-audit list.

Deducting in a no-PT state. A payroll template gets cloned when a new location opens and PT comes along for the ride. Now you're deducting from employees in a state with no levy. This is not a harmless over-deduction — you have taken money you had no authority to take, you probably can't remit it anywhere, and you owe it back with an explanation.

Wrong state mapping for remote workers. Covered above. The tell is that your PT state distribution doesn't match your actual office footprint.

Missing registration when entering a new state. You hired in a new PT state in April, you started deducting in May, but you only got registered in September. The deductions were made without authority, the remittances are late, and the interest clock has been running.

Never obtaining the entity's own enrolment. The PTRC/PTEC gap. Employer deductions are perfect; the company's own liability has never been paid.

Forgetting to renew or maintain the enrolment certificate. Some states require periodic renewal or annual payment against the enrolment. It falls off the calendar because it doesn't touch payroll and nobody owns it.

Not deducting for directors and partners where applicable. Founders exempt themselves by inattention rather than by rule.

Missing the higher-deduction month. The February problem. Twelve equal deductions where the state prescribed eleven plus one larger one.

Not updating slabs after a state revision. Your table is three years old. Nobody checks, because PT is small and nobody complains when it's too low.

Treating a temporary transfer as a permanent one, or vice versa. Deputations and long client site postings need a decision, not drift.

Stopping deduction for an employee on long leave without checking the rule. Assumed rather than verified.

Rounding inconsistently. Small, but it makes reconciliations fail and creates noise that hides real errors.

No reconciliation between payroll register, challan and return. The single highest-value control, and the one most often skipped.

Returns, Filings and Record Keeping

Every PT state expects some combination of periodic payment and periodic return. Forms, portals and frequencies are all state-specific, and we are intentionally not listing due dates or form numbers because they change.

What is consistent is the evidence trail you should be able to produce for any month, in any state, within a few minutes:

1. Employee-level PT register — name, employee code, work location state, salary measure used, slab applied, amount deducted.
2. State-wise summary — headcount and total liability per registration certificate.
3. Challan or payment proof — with the certificate number visible and the amount matching the summary.
4. Filed return and acknowledgement — with the period clearly identified.
5. Reconciliation — a short statement tying the payroll register total to the challan total to the return total, with any difference explained.
6. Configuration notes — which slab version was applied, from what effective date, and the source you verified it against.

That last item is what separates a defensible position from a guess. Write down the URL and the date you checked the state portal. When a rate turns out to have changed, you will be able to show exactly when your information was current.

Retention

Retain PT records for the period your state's law requires, and as a practical matter align PT retention with your general statutory payroll retention policy — it is simpler to keep one retention rule than seven. Keep records in a form that survives a payroll vendor change. If your PT registers only exist inside a system you might switch away from, export them periodically.

Penalties and Interest: The Shape of the Risk

We will not quote rates or amounts, because they vary by state and get revised. But you should understand the categories of exposure, because they compound differently.

• Interest on late payment. Accrues from the due date until payment. Usually the smallest component in rupee terms, but it runs silently.
• Penalty for late payment or non-payment. Often a separate charge on top of interest, sometimes discretionary.
• Penalty for late filing of returns. Can apply even where the tax was paid on time. Filing and paying are separate obligations.
• Penalty for failure to register or enrol. Often calculated by reference to the period of delay, which is why discovering an old gap is worse than discovering a recent one.
• Penalty for false or incorrect statements. Applies to returns, not just payments.
• Prosecution provisions. Present in several statutes for persistent default. Rare in practice for SMBs acting in good faith, but they exist.

The structural point: the employer carries the liability even though the employee is the taxpayer. If you failed to deduct, the state pursues you, not your employees. You cannot deflect a PT default onto staff.

The secondary point: the amounts are small enough that the real cost is rarely the tax. It's the time, the professional fees, the diligence finding during a fundraise, and the awkward conversation with employees whose payslips you now have to correct.

PT, Take-Home Salary and the Payslip

PT is a deduction from gross pay, so it reduces take-home. It is not a cost to the employer in the way PF or ESI employer contributions are — you are deducting from the employee's own money and passing it on. The entity's own enrolment liability is a company cost; the employee deduction is not.

This distinction matters in two conversations you will have repeatedly.

In offer letters and CTC discussions. PT should not be shown as a component of CTC, because it is not an employer cost. It appears in the gross-to-net bridge, below gross, alongside income tax and the employee's PF share. Employers who bundle it into CTC create confusion at offer stage and disputes later.

With employees who moved states. An employee transferring from a no-PT state to a PT state will see a new deduction and a slightly lower net. An employee transferring the other way will see a deduction disappear. Both will ask. Have a one-paragraph explanation ready that names the state, the levy, and the fact that it's statutory.

Payslip Presentation

Show PT as its own named line. "Professional Tax" — not "Other deductions," not "Statutory deduction," not merged with anything. Where you operate in multiple states, consider adding the state name so the employee can see why their colleague's payslip differs.

Illustrative gross-to-net view (placeholder numbers, not real slabs):

Transparent presentation is also a compliance asset. If an employee later queries a deduction, a clearly labelled payslip line plus your PT register is the whole answer.

PT and the New Labour Codes: Why Now Is a Good Moment

India's four labour codes came into effect in late 2025, and most employers have spent the period since then reworking the wage structures that underpin payroll. The codes bring a harmonised statutory definition of wages, with consequences for how basic pay, allowances and variable components are composed — which in turn moves gratuity, leave encashment and retirement fund calculations.

PT is a state levy and sits outside the labour codes. The codes do not change PT rates or PT law. But the restructuring work they triggered creates a practical opportunity that is worth taking.

Here's why. If you are already reopening salary structures, recomputing components and re-testing what falls inside and outside the wage definition, you are already touching every field that feeds a PT slab test. The marginal cost of also checking your PT configuration — state mapping, slab versions, annual totals, registration coverage — is low right now and high later.

Three specific overlaps deserve attention during a wage-structure review:

• Changed gross composition can move slab positions. If restructuring shifts amounts between components, and your state's PT base is a subset of gross rather than the whole of it, some employees may cross a slab boundary in either direction. Re-test, don't assume.
• Re-papered contracts are a chance to fix work location. If you are issuing revised appointment letters or addenda anyway, make sure the stated work location is accurate for remote and hybrid staff. That field drives PT.
• A single compliance calendar beats several. Teams building or rebuilding a statutory calendar for the codes should fold state PT deadlines into the same artifact rather than keeping PT in a separate spreadsheet that only one person opens.

Treat the codes as the trigger, not the reason. PT obligations existed before and continue unchanged; the restructuring simply gives you a natural window to clean them up.

The Month-End PT Checklist

Run this every payroll cycle, per state. It takes a competent payroll person under thirty minutes once the data is structured properly.

1. Confirm the employee list per PT state. Pull headcount by work location, not by address. Compare with last month and investigate every addition and removal.
2. Check joiners. Does each new joiner have a work location, a PT state, and a correct first-month treatment?
3. Check leavers. Was final-settlement PT handled per the state rule?
4. Check state changes. Any transfers, relocations or work-location updates this month? Did PT follow?
5. Check LOP cases. Any employee whose earnings changed enough to move slabs? Is that the correct treatment for that state?
6. Check arrears and off-cycle payments. Did any of them affect the slab test under your documented method?
7. Verify slab tables are current. At minimum, confirm nothing has changed on the state portal at the start of each quarter and whenever a state budget lands.
8. Check for the special higher-deduction month. Does any state in your footprint prescribe a different amount this month?
9. Reconcile the register to the payroll totals. State-wise sums must tie exactly.
10. Confirm zero-deduction states really are zero. Verify that no PT is being deducted in your no-PT locations.
11. Deposit before the internal deadline. Per certificate, per state.
12. File the return where due this period. Save the acknowledgement with the challan.
13. Archive the month's pack. Register, summary, challan, return, reconciliation note — one folder, per state, per month.

A Quarterly Add-On

Once a quarter, also check: entity enrolment payments are current, registration certificates are valid and not pending renewal, any new state you entered has a registration in place, and your slab version history is complete for the periods you might need to re-run.

The Multi-State Expansion Checklist

Use this before, not after, you make an offer in a new state.

1. Determine whether the state levies PT. Confirm on the state government portal. Do not rely on a blog — including this one — for applicability.
2. Identify the administering authority. State department, or local body? If local, which municipality?
3. Determine registration obligations. Employer registration, entity enrolment, or both. Note the trigger — often the first employee, or the establishment of a place of business.
4. Check whether a place of business is required or created. Some registrations assume a physical establishment; a fully remote hire may raise questions worth taking advice on.
5. Note the timelines. Many states require registration within a short window of becoming liable. Late registration is a separate penalty head from late payment.
6. Gather documents early. Incorporation documents, PAN, address proof, authorised signatory details, employee list, bank details. Requirements vary; collect the superset.
7. Obtain the certificate before the first payroll run in that state. If the certificate isn't ready, know exactly what your fallback treatment is and document it.
8. Load the slab schedule with effective dates. Into your payroll system, versioned.
9. Map the work location. Create the location, link it to the PT state and certificate, assign employees to it.
10. Add the state to the compliance calendar. Deposit frequency, return frequency, internal deadlines, named owner.
11. Run a parallel first month. Compute manually and compare with system output before you rely on it.
12. Brief the employees. A short note explaining the new deduction prevents a wave of tickets.

What to Do If You Discover a Past Under-Deduction

It happens. You open a new state, hire in it, and six months later realise nothing was deducted. Or you find your Karnataka slabs were two revisions out of date. Panic is not useful; a structured remediation is.

Step 1: Scope It Precisely

Before you fix anything, quantify it. Build a simple matrix: employee × month × state × amount that should have been deducted × amount actually deducted × difference. Do not estimate. The numbers are small enough that exact computation is feasible, and an exact number is what you need for both the decision and the disclosure.

Remember the annual ceiling per person per state — it bounds your worst case and often makes the total far less alarming than it felt at first.

Step 2: Fix the Root Cause

Correct the configuration before you correct the history, otherwise you will be remediating the same issue again next quarter. Update slab tables, fix state mapping, complete the registration, add the calendar entry, assign an owner.

Step 3: Decide Who Bears the Shortfall

You have three practical options, and the choice is partly legal and partly a people decision:

• Recover from employees in future payrolls. Defensible, since the tax was always theirs — but recovering several months at once is a visible hit to take-home, and depending on the state and the amounts involved there may be limits on the deductions you can make from wages. Take advice before doing this at scale.
• Absorb it as an employer cost. Clean, fast, avoids employee friction, and for typical SMB headcounts the total is often modest. Most employers choose this for genuine employer-side errors.
• A split approach. Absorb the older periods, recover the recent ones, communicate clearly. Workable, but it needs to be explained well or it reads as arbitrary.

Whatever you choose, apply it consistently across everyone affected. Differential treatment of employees in the same situation is the thing that turns a compliance cleanup into a grievance.

Step 4: Regularise With the State

Register or enrol if that was the gap. Deposit the arrears against the correct certificate. File or revise returns as the state's procedure allows. Expect interest, and possibly penalty. Pay it and move on rather than arguing over small sums.

Voluntary regularisation before any notice is almost always viewed more favourably than a default discovered by the department. The clock works against you; speed is worth more than deliberation here.

Step 5: Document the Whole Episode

Write a short internal memo: what happened, the period affected, how it was quantified, what was paid and when, who decided the recovery approach, and what control was added to prevent recurrence. This memo is what you hand to a diligence team or an auditor later, and it converts an embarrassing finding into evidence of a functioning control environment.

Step 6: Add the Control

One new check, tied to a person and a date. For a registration gap, add "confirm PT registration exists" to your new-state checklist. For a stale-slab gap, add a quarterly portal check. Controls that aren't specific and owned don't survive the next busy quarter.

Building a PT Governance Routine

For a 50-to-500 person SMB operating in three to eight states, a workable governance model looks like this:

• One named owner for state-level statutory levies, with PT explicitly in their remit. Not "finance" — a person.
• A single compliance calendar covering every state, every obligation type, with internal deadlines ahead of statutory ones.
• Versioned configuration in the payroll system, with change logs.
• A monthly reconciliation that ties register to challan to return, signed off by someone other than the preparer.
• A quarterly rate review against state portals, with the check date recorded.
• An annual reconciliation of twelve months' deductions per employee per state against the state's prescribed annual total.
• An expansion gate so that no new state goes live in payroll without the registration and configuration checklist being complete.

None of this is expensive. All of it is cheaper than remediation.

Frequently Asked Questions

Is professional tax the same in every Indian state?

No. Professional tax is a state subject, and every state that levies it sets its own slabs, thresholds, registration process, return formats and due dates. Some states and union territories don't levy it at all. There is no central rate and no national portal, which is exactly why multi-state employers need per-state configuration rather than a single payroll rule. Always confirm the current schedule on the specific state's commercial tax or PT department website.

Do I deduct PT based on where the employee lives or where they work?

Work location, as a general rule. PT applies to employment exercised within a state, so the relevant state is where the person actually renders services — not their residential address in your HRIS. This is the single most common source of PT errors, because many payroll systems default to pulling the state from the personal address field. Fix that mapping first.

What's the difference between PTRC and PTEC?

PTRC-type registration is the employer's authority and obligation to deduct PT from employees' salaries and remit it to the state. PTEC-type enrolment is the tax the business entity itself pays for carrying on a trade or profession in that state, independent of employees. Most companies operating in a PT state need both. Terminology differs by state, so check the state's own forms rather than assuming Maharashtra's naming applies everywhere.

We hired a remote employee in a state where we have no office. Does PT apply?

It depends, and this is genuinely one of the less settled areas. The starting question is where the employment is being exercised, which points toward the state the person works from. But whether you have an establishment there, what the contract says, and whether the arrangement is permanent all matter. Take advice for anything more than a handful of people, adopt a documented position, and apply it consistently rather than case by case.

What happens if we've been under-deducting for several months?

Quantify it exactly, fix the configuration, decide whether to recover from employees or absorb the cost, regularise with the state by depositing arrears and filing or revising returns, and document the whole episode internally. The employer carries the liability even though the employee is the taxpayer, so you cannot simply pass the default along. Voluntary correction before a notice arrives is treated far better than a discovered default. Interest and possibly penalty will apply — confirm the current charges with the state.

Do directors and partners have to pay professional tax?

Often yes, though the mechanism varies. Directors drawing remuneration may be covered as employees in some states; partners and proprietors are commonly covered under the enrolment route. Founders regularly overlook their own liability while managing employee deductions perfectly. Check the specific state's treatment, because states differ on whether a director without a genuine employer-employee relationship is covered.

Why is one month's PT deduction higher than the others in some states?

Because the annual total prescribed for a slab doesn't always divide evenly into twelve equal instalments, so the state designates one month — commonly February — with a different amount to make the year add up. Payroll systems that hard-code a fixed monthly figure miss this for eleven months and then produce a short year-end total. Configure the annual schedule and reconcile twelve months against the prescribed annual amount.

Conclusion

Professional tax compliance is not intellectually hard. It is operationally unforgiving. The rules are simple enough to explain in an afternoon, but they multiply across states, and each multiplication introduces a place where a work location can be wrong, a slab table can go stale, a registration can be missing, or a February deduction can be flat when it shouldn't be.

The employers who get PT right are not the ones with the best tax knowledge. They are the ones who treated it as a configuration and calendar problem: work location drives the state, the state drives the certificate and the slab, the slab tables are versioned, every state has a deadline with a named owner, and every month the register reconciles to the challan and the return. Do that, and PT stops being a source of surprises.

Two things to take away. First, verify before you configure — slabs, thresholds and due dates change, and the only reliable source is the relevant state government or commercial tax department portal on the day you check it. Second, if you are already reworking salary structures in the wake of the labour codes, fold a PT review into the same exercise. You are touching the underlying data anyway, and a cleanup done alongside existing work costs a fraction of one done under a notice.

If managing PT across multiple states is currently living in a spreadsheet, CozyHR can take most of it off your plate — state-wise slab configuration mapped to work location, automatic deduction across multi-state payrolls, remittance and return reminders per registration, and ready state-wise PT registers for your records. Worth a look if your next hire is in a state you haven't run payroll in before.