Professional Tax in India: State-Wise Employer Guide

Professional tax is the compliance item that most Indian employers get wrong at exactly the moment they can least afford it — when they start hiring outside their home state. It is a small deduction, often a rounding error on a payslip, and precisely because it is small it slips out of the payroll review. Then a state commercial tax department sends a notice, and a founder discovers the company has been employing people in three states while holding a registration in one.

This guide is written for HR managers, founders and payroll teams running Indian payroll in 2026, particularly those with distributed, remote or hybrid teams. It covers what the levy actually is, why it is a state subject and not a central one, which states commonly impose it, the two registrations you will hear about (PTEC and PTRC), how slab-based deduction works, monthly versus annual filing, the messy questions around remote employees and mid-year transfers, and how to run the whole thing as a repeatable monthly process instead of a quarterly panic.

A standing caution before we begin, and it applies to every number in this article: slabs, thresholds, due dates and penalty provisions vary by state and are revised by state notifications and finance acts. Every figure used below is illustrative and exists only to demonstrate mechanics. Verify the current position for each state you operate in with that state's commercial tax or profession tax department portal, or with your tax advisor, before you configure payroll.

What Professional Tax Actually Is

It is a tax on professions, trades, callings and employments. State governments (and some union territories) levy it on people who earn a living within that state, whether as salaried employees, self-employed professionals, or businesses.

Two things confuse people immediately.

First, the name. "Professional" implies it applies only to doctors, lawyers and chartered accountants. It does not. A salaried data entry operator and a partner at a law firm are both potentially within scope. The word is doing much less work than it appears to.

Second, it has nothing to do with income tax. It is not a TDS. It is not administered by the Income Tax Department. It does not appear in Form 26AS. It is a separate levy with separate registrations, separate returns, separate portals and separate officers — one set per state.

Why It Is a State Levy, Not a Central One

The constitutional basis matters, because it explains why you cannot have a single national process.

The Constitution of India permits state legislatures to tax professions, trades, callings and employments. It also caps how much a state may collect from any one person in a financial year under this head. That ceiling is the reason the levy stays a modest annual amount rather than growing into a meaningful revenue line — states can adjust slabs within the cap, but not beyond it.

The practical consequences of state-level administration are the whole reason this article needs to be several thousand words long:

• Each state writes its own Act and Rules. Maharashtra's statute, Karnataka's statute and West Bengal's statute are different laws with different definitions, different registration nomenclature, different return forms and different calendars.
• Each state sets its own slabs within the constitutional ceiling, and revises them at its own pace, usually through the state budget or a standalone notification.
• Each state runs its own portal. Login credentials, challan formats, return forms and payment gateways differ.
• Some states do not levy it at all. This is a policy choice, and it can change.

There is no GST-style unification here. A company with offices in six states may hold six separate sets of registrations, file six different return cycles, and track six sets of slab tables. This is the single biggest reason the levy becomes unmanageable on spreadsheets.

Who Pays, and Who Deducts

The levy operates through two distinct liabilities that people constantly conflate.

The employer's own liability. The business entity itself — company, LLP, partnership, proprietorship — is a "person engaged in a profession or trade" in the eyes of the state. It therefore owes tax on its own account, typically an annual amount, sometimes graded by the type or size of entity. Directors and partners may have separate liabilities in some states. This is enrolment-type liability.

The employer's liability as a deductor. Separately, the employer is obliged to deduct from the salary of each employee working in that state, and remit it to the state. The employee bears the cost; the employer is the collection agent and is liable for failure to collect and remit. This is registration-type liability.

These two are not alternatives. A company with employees in a levying state generally needs both. A company with no employees in that state but a registered place of business may still need the first. Holding only one of the two is one of the most common gaps in SMB payroll.

Which States Levy It, and Which Generally Do Not

The levy is commonly imposed in states and UTs such as:

Maharashtra, Karnataka, West Bengal, Tamil Nadu, Telangana, Andhra Pradesh, Gujarat, Madhya Pradesh, Kerala, Odisha, Assam, Bihar, Jharkhand, Meghalaya, Sikkim, Tripura and Puducherry — verify your state.

It is generally not levied in states and UTs such as:

Delhi, Haryana, Uttar Pradesh, Rajasthan, Punjab, Himachal Pradesh, Uttarakhand, Goa, Chandigarh and Jammu & Kashmir — again, confirm the current status before you rely on this.

Treat both lists as an orientation map, not a legal conclusion. Three caveats deserve emphasis:

1. Status can change. A state that does not levy today can introduce it; a state that levies it can restructure or withdraw it. Legislative changes do happen, and payroll teams find out late.
2. Administration can be local. In some states, tax on trades and callings is collected by local bodies — municipal corporations or panchayats — rather than a single state department. Kerala is the classic example of local-body-driven administration, which means your obligation can depend on which municipality your office sits in, not just which state.
3. Coverage is not uniform even within a levying state. Some states exempt categories of persons — certain senior citizens, persons with specified disabilities, parents or guardians of children with disabilities, certain armed forces personnel, and others. Exemption lists are state-specific and are among the more commonly missed items in payroll configuration.

The operating rule for a multi-state employer: maintain a state register that records, for each state where you have employees or premises, whether the levy applies, under which Act, which registrations you hold, and when you last verified the slabs. We build that register later in this article.

The Two Registrations: PTEC and PTRC

Maharashtra's terminology has become the industry shorthand, so most Indian payroll professionals use these two acronyms regardless of the state they are discussing.

PTEC — Professional Tax Enrolment Certificate

The enrolment certificate covers the entity's own liability. Think of it as "the business pays for itself."

• Held by the company, LLP, firm or proprietor.
• Typically results in a fixed annual payment rather than a monthly computation.
• In some states, working partners, directors or the proprietor personally need enrolment as well.
• Usually required even where the entity has few or no employees in the state, provided it has a place of business there.

PTRC — Professional Tax Registration Certificate

The registration certificate covers the obligation to deduct from employees and remit.

• Held by the employer in its capacity as deductor.
• Drives monthly or annual returns, depending on state rules and the employer's liability or turnover.
• Required once you have employees drawing salary above the state's threshold in that state.

Naming Varies — Do Not Assume

Different states use different words for the same two ideas. You will encounter:

• "Enrolment certificate" and "registration certificate" (Maharashtra-style).
• "Certificate of enrolment" and "certificate of registration" (West Bengal-style).
• "Employer registration" and "self-employed enrolment" phrasing.
• States where both are issued as a single consolidated number, and states where they are entirely separate applications on separate forms.

The rule to internalise is conceptual, not lexical: there is an entity-level liability and a deduct-and-remit liability, and you need to determine separately whether each applies in each state. If you approach a new state by asking "do we need the entity registration, and do we need the deductor registration?", the local form names sort themselves out.

Documents Typically Requested at Registration

Requirements differ, but most state portals ask for some combination of:

Two practical notes. First, the date of commencement of business or employment matters: several states compute liability from that date, so a late application can generate arrears for months you never filed. Second, many portals require a digital signature or an OTP-based authentication tied to a specific person — if that person leaves the company, the reauthorisation process can take weeks. Document who holds portal credentials for each state.

How Slab-Based Deduction Works

Nearly every levying state uses a slab structure based on monthly gross salary or wages. You place the employee in a band, and the band determines a flat rupee amount for the month. It is not a percentage of salary, and it is not progressive in the income-tax sense — there is no marginal computation across bands. One band, one amount.

The generic shape looks like this:

ILLUSTRATIVE ONLY — not any state's actual slab. Verify your state's current notification.

Do not copy those numbers into your payroll system. They exist to explain mechanics only.

The Four Configuration Questions

For each state, your payroll configuration needs an answer to four questions. Getting any one wrong produces a systematic error repeated across every employee, every month.

1. What is the base? Is the slab applied to gross salary, to basic plus DA, to "salary and wages" as defined in that state's Act, or to a defined subset? States differ, and the definition in the Act may include or exclude items like bonus, overtime, leave encashment, reimbursements and employer contributions. A company that applies gross where the Act says basic-plus-DA will over-deduct across the board.

2. Which month's salary decides the band? Most states look at the salary payable for the month in question. That means a variable-pay month can push an employee into a higher band for that month only. Decide whether your system re-evaluates the band monthly or freezes it annually, and make sure that choice matches the state's rules rather than your convenience.

3. Is there a gender-based or category-based differential? Some states have historically prescribed a higher exemption threshold for women employees, and several prescribe exemptions for specified categories such as senior citizens or persons with disability. These are state-specific and change; they must be modelled as employee attributes, not hardcoded.

4. Is there a special month with a different amount? Several states levy a higher amount in one designated month of the year so that the annual total lands exactly on the statutory ceiling. We deal with this separately below, because it is the single most common source of annual reconciliation mismatches.

Worked Example 1 — Single State, Steady Salary

Priya works in a levying state. Her monthly gross is Rs 45,000 and it does not vary.

Using the illustrative table above, she sits in the top band at Rs 210 per month.

The point of this table is not the arithmetic — it is that an annual total built from eleven identical months plus one different month is the pattern you must be able to reproduce. If your reconciliation expects twelve identical deductions, you will chase a phantom variance every February.

Worked Example 2 — Variable Pay Pushes a Band

Rahul's fixed monthly gross is Rs 17,500, which places him in the second illustrative band at Rs 130. In September he receives a performance incentive of Rs 9,000 paid through payroll.

• September gross becomes Rs 26,500.
• If the state's base includes incentives, September moves him into the top band: Rs 210 instead of Rs 130.
• The following month he returns to Rs 130.

Two things follow. First, your payroll engine must re-evaluate the band on actual monthly earnings, not on a stored CTC field. Second, whether the incentive counts at all depends on the state's definition of salary and wages — which is question 1 above. Confirm it; do not assume.

Worked Example 3 — Mid-Month Joiner and Leaver

Ananya joins on 18 September and her first month's earnings are prorated to Rs 9,000, below the illustrative threshold. In October she earns her full Rs 32,000.

• September: prorated earnings fall below the exemption threshold, so no deduction under the illustrative table.
• October onward: top band applies.

This is correct under a "salary payable for the month" reading — but some states expect the band to be determined on the full-month equivalent rather than the prorated figure. The two readings produce different answers for every joiner and leaver you process. Pick the reading your state's Act supports, document the choice in your payroll SOP, and apply it consistently. Inconsistency across employees is what turns a technical question into an audit finding.

Worked Example 4 — Loss of Pay

Vikram's normal gross is Rs 20,000, second band, Rs 180 illustrative. He takes 12 days of unpaid leave in June and earns Rs 12,000 that month.

If your state determines the band on actual earnings, June's deduction falls to the lower band or to nil. If it determines the band on contractual salary, the deduction stays at Rs 180. The same person, same month, two defensible answers depending on the state. This is exactly the kind of thing that should live in a configured rule in your HRMS rather than in an analyst's memory.

Monthly Versus Annual Filing

The filing frequency for the deductor registration is not a matter of preference. States set it, usually by reference to one of two triggers.

Trigger 1 — prior-year tax liability. Many states apply a threshold: if your total remittance for the previous financial year exceeded a specified amount, you file monthly; below it, annually. The threshold is a rupee figure set by state notification.

Trigger 2 — employee count or turnover. Some states key the frequency to headcount or business turnover instead of, or in addition to, prior liability.

Whatever the trigger, three practical consequences follow.

• Frequency can change year to year. A company that files annually in one year may cross the threshold and become a monthly filer the next. This transition is a classic miss: the team keeps the old calendar and discovers eleven late returns.
• The entity registration and deductor registration have different rhythms. The entity liability is usually an annual payment on a fixed date; the deductor obligation may be monthly. Do not merge them into one reminder.
• A nil return is still a return. In most states, if you hold an active deductor registration you must file even in a month where no deduction arose — a month where all employees are below the threshold, or where a branch is temporarily unstaffed. Dormant registrations accumulate late-filing exposure quietly.

The Special Month Variation

Several states structure their annual amount so that eleven months carry one figure and one designated month carries a higher figure, landing the total at the constitutional ceiling. Maharashtra's use of February for this pattern is the best-known example; other states use their own designated month, or no special month at all.

Three implementation notes:

1. Configure it as a rule, not a manual override. A manual February adjustment applied by one person is a single point of failure. When that person is on leave, the adjustment is missed and you get a shortfall that surfaces in the annual reconciliation.
2. Handle mid-year exits. An employee who resigns in December in a state with a February variation never pays the higher amount. That is normally correct — but your annual reconciliation must expect it, or every leaver looks like an error.
3. Handle mid-year joiners. Someone joining in January in the same state pays the higher amount in their second month. Again, correct, and again, it must be anticipated in reconciliation.

The Hard Part: Multi-State and Remote Employees

This is where professional tax stops being a payroll formatting exercise and becomes a genuine compliance question. It is also where the standard answer — "deduct for the state where the employee works" — starts to fray, because "works" is doing an enormous amount of undefined work in a hybrid world.

The Governing Principle

The levy attaches to employment exercised within the state. In the simple case, an employee reports to an office in a state, the employer has a place of business in that state, and the state's Act applies. Everything difficult is a variation on establishing where employment is exercised and whether the employer has a taxable presence there.

Scenario A — Fully Remote Employee in a Different State

Your company is registered in Karnataka. You hire a developer who lives and works entirely from Jaipur, Rajasthan, and never visits an office.

The questions to work through, in order:

1. Does the employee's state levy the tax at all? If they are in a state that does not levy it, the immediate answer is that there is nothing to deduct there. Rajasthan is generally in the non-levying group — but confirm current status, because this is exactly the kind of thing that changes.
2. Does the employer have a taxable presence in the employee's state? Most state Acts tie the deduction obligation to an employer with an establishment or place of business in that state. A single work-from-home employee may or may not create one, depending on the state's definition and on how the arrangement is documented.
3. Which state's office is the employee attached to on record? If the employee is on the payroll of the Bengaluru establishment, is paid from it, reports into it and appears in its muster roll, a common and defensible position is that Karnataka's rules apply to them.
4. What does the state say specifically about remote work? Some states have issued clarifications; many have not. Where the position is genuinely unsettled, this is an advisor question, not a payroll-configuration question.

The honest summary: there is no single national rule for remote employees, and any confident one-line answer should be treated with suspicion. What you can do is adopt a written, consistent policy, apply it uniformly, and revisit it annually.

Scenario B — Employee Transfers Mid-Year

Meera works in Maharashtra from April to October, then transfers to Telangana from November.

The general approach:

• April to October: deduct under Maharashtra's rules, remit against the Maharashtra registration.
• November to March: deduct under Telangana's rules, remit against the Telangana registration.
• Her Form 16 and payslips should reflect the split, and both states' annual returns should show her for the relevant part-year.

The complications are real:

• Special-month timing. If Maharashtra's higher February amount applies and she left Maharashtra in October, she does not pay it there. If Telangana has its own variation in a different month, she may pick that up instead. Your annual reconciliation must handle the crossover cleanly.
• Ceiling awareness. The constitutional cap applies per person per year. An employee who works in two levying states in one year can, on a mechanical application of both states' slabs, be deducted more than the annual cap in aggregate. How that is treated is a genuinely technical question — raise it with your advisor rather than improvising.
• Effective date discipline. The transfer date in your HRIS must match the date used for the deduction switch. If HR records the transfer as 1 November and payroll switches from 1 December, both states' records are wrong for a month.

Scenario C — Employee Splits Time Across Two State Offices

A regional sales manager based in Chennai spends roughly ten days a month at the Hyderabad office.

There is no universally accepted apportionment mechanism. The workable positions are:

• Base-location approach. Deduct for the state of the employee's designated base location — the establishment they are on the rolls of. This is the most common practice, the easiest to administer, and the easiest to explain to an officer.
• Substantial-presence approach. If the employee is in fact performing employment substantially in a second state, and your establishment there has its own registration and muster roll, the second state may expect to see them.

Whatever you choose, document it. The defensible position is a written policy applied consistently across every employee in the same situation. The indefensible position is a per-employee judgement call made by whoever happened to run payroll that month.

Scenario D — Coworking Spaces and Satellite Presence

The one that catches growing companies. Sales hires a person in a new city, books three desks in a coworking space, and no one tells finance. Twelve months later the company has an operating presence in a state where it holds no registration.

Two safeguards, both cheap:

• Make the new-state trigger explicit in your hiring workflow. Any offer with a work location in a state where you have no registration should route to finance before it is released, not after the person joins.
• Reconcile your employee state map to your registration map every quarter. Two lists, one comparison. Any state in the first list that is missing from the second is an open item.

Professional Tax on the Payslip

The deduction sits on the payslip as a distinct line item, and it needs to be labelled properly. Employees ask about it more than you would expect, largely because it is unfamiliar and appears without explanation.

Where It Sits in the Salary Structure

A conventional Indian payslip shows:

Show it as its own line, named clearly — "Professional Tax" or "PT". Do not bundle it into an "Other deductions" bucket. Bundling generates queries, makes reconciliation harder, and looks careless during an inspection.

Two presentation practices worth adopting:

• Show the state. On a payslip for a multi-state employer, "Professional Tax (Karnataka)" removes an entire category of employee question and makes the payslip self-documenting for audit.
• Show a year-to-date column. Employees who moved states mid-year, and anyone comparing their payslip to their tax computation, will need it.

Interaction With Income Tax

There is a genuine interaction with income tax, and it is one of the few places where the two regimes touch.

Under the Income-tax Act, a deduction is available for taxes on employment paid by an employee — the professional tax borne by them. This has historically been claimed against salary income, and it is the reason the deduction should be tracked accurately per employee per year, not just remitted in bulk.

Three points of practical importance:

1. Availability depends on the tax regime the employee has chosen. The old and new regimes treat deductions differently, and the treatment of employment tax is not identical across them. The rules here have moved in recent years. Confirm the current position for the relevant assessment year before you configure your TDS engine — do not carry forward last year's logic without checking.
2. It is generally allowed on a paid basis. The deduction typically follows actual payment during the year rather than accrual, which matters when a February amount is remitted in March, or when arrears are cleared late.
3. It must flow into Form 16 correctly. If your payroll system deducts it but your TDS computation does not reflect it where allowable, you over-deduct income tax and generate refund claims and employee complaints. This is a systems-integration issue, and it is a good reason to run payroll and TDS computation from the same source of truth rather than reconciling two systems by hand.

Consequences of Non-Compliance

Every levying state's Act contains enforcement provisions. The specific rates, percentages and amounts differ by state and change over time, so what follows describes the categories of exposure rather than quoting figures. Check your state's Act and current notifications for the actual numbers.

The Categories of Exposure

Interest on late payment. Where tax is deducted but remitted late, states generally charge interest for the period of delay. This runs automatically and does not require an officer to take a view.

Penalty for late or non-filing of returns. Typically a fixed amount per return or per period of default. Because it is per return, a company that discovers three years of unfiled returns across four states is looking at a multiple of a small number, which becomes a large number.

Penalty for failure to register. States commonly penalise operating without the required certificate, often computed by reference to the period of non-registration. This is the one that hurts multi-state employers, because the clock starts when you began employing in the state — not when you noticed.

Penalty for failure to deduct. Where an employer fails to deduct from employees at all, the employer generally remains liable for the amount, plus consequences. Recovering it from employees retrospectively is awkward at best and often impractical for people who have since left.

Recovery proceedings. In serious or prolonged cases, states have recovery powers including attachment. This is rare for ordinary SMB defaults, but it exists.

What Actually Triggers Enforcement

In practice, the common trigger events are:

• A registration application in a new state that prompts questions about when the company began employing there.
• A departmental inspection or survey of the establishment.
• Cross-referencing with other registrations — GST, shops and establishments, EPFO — which reveals a presence the department did not have on record.
• An employee complaint, sometimes from a departing employee who noticed a deduction that was never reflected anywhere.
• Due diligence during fundraising or an acquisition. Multi-state compliance gaps are a standard diligence checklist item, and unresolved ones become indemnities or holdbacks.

That last one is worth dwelling on. The rupee amounts involved are small. The diligence friction is not. A founder who has to explain an unregistered state to an acquirer's counsel spends far more on that conversation than the underlying tax was ever worth.

If You Find a Gap

Do not improvise, and do not simply start deducting from the current month while hoping nobody looks backwards. A workable sequence:

1. Quantify. Which states, which periods, how many employees, what approximate amount. Get the facts before you get advice.
2. Take advice. State-specific voluntary compliance, waiver or amnesty mechanisms have existed at various times. Whether one is currently open in your state is precisely the kind of question a local advisor answers in ten minutes.
3. Regularise registration first. In most cases the registration has to exist before arrears can be paid against it.
4. Document the remediation. A dated internal note recording what you found, what advice you took and what you paid is the single most useful artefact in a future diligence.
5. Fix the process. A gap that recurs after being fixed once is a much worse fact pattern than a gap that was found and closed.

A Month-by-Month Operating Calendar

Here is a template calendar for a multi-state employer. The dates are placeholders. Actual due dates differ by state and by whether you are a monthly or annual filer. Populate the placeholders from each state's current notifications and then treat this as your operating rhythm.

Two design notes. First, name an owner for every row. Compliance items without a named owner are the ones that lapse. Second, keep the "on event" rows in the same document as the calendar rows. The event-driven items are the ones that create the largest exposures, and they are invisible to a purely date-driven reminder system.

Compliance Checklist

Run this quarterly. It takes under an hour once the underlying records exist.

Registrations

• [ ] Every state where we have employees is on our state map
• [ ] Every state on the map has a documented answer: levies / does not levy / verify
• [ ] Entity-level registration obtained in every state where required
• [ ] Deductor registration obtained in every state where we have employees above the threshold
• [ ] Directors, partners or proprietor enrolled where the state requires it
• [ ] Certificate copies stored centrally with numbers, dates and issuing office
• [ ] Portal credentials documented, with a named holder and a backup

Deduction accuracy

• [ ] Current slab table loaded for every state, with the date last verified
• [ ] Salary base per state configured correctly (gross vs basic-plus-DA vs statutory definition)
• [ ] Exemption categories configured as employee attributes, not manual overrides
• [ ] Special-month rule configured where applicable
• [ ] New joiners and leavers handled per a documented and consistent proration policy
• [ ] Employees in non-levying states correctly excluded, and the exclusion documented

Remittance and filing

• [ ] Challans generated and paid by each state's due date
• [ ] Challan numbers, dates and amounts recorded against the payroll period
• [ ] Returns filed at the correct frequency for the current year in every state
• [ ] Nil returns filed where an active registration exists but no liability arose
• [ ] Filing frequency reassessed at the start of the financial year

Reconciliation and records

• [ ] Deducted equals remitted equals filed, per state, per month
• [ ] Per-employee annual totals available for the income tax computation
• [ ] Payslips show the deduction as a distinct, correctly labelled line
• [ ] Registers and records maintained per state requirements
• [ ] Prior-period differences investigated and documented, not just written off

Multi-State Registers and Records

Most state Acts require an employer to maintain specified registers and to produce them on demand. The exact forms are state-specific. What follows is a template for the records a multi-state employer should hold centrally, mapped to why each matters.

Retention periods above are prudent practice, not a citation of any particular state's statutory minimum. Confirm the requirement for your states.

A note on storage. Keep these centrally, not in the local finance person's folder in each city. The most common failure mode is not that records were never created — it is that the person who created them left, and nobody else knew where they were.

How an HRMS Automates the Whole Thing

Everything above can be done on spreadsheets. It is done on spreadsheets at thousands of Indian SMBs right now. It works until you cross roughly two states and fifty employees, and then it stops working in a specific and predictable way: the spreadsheet stays correct, but it stops being updated.

Here is what moving professional tax into an HRMS actually changes, function by function.

1. State Mapping Becomes Automatic

Instead of a payroll analyst remembering that three people moved from Pune to Hyderabad in November, the system holds a work location on the employee record with effective dates. Every payroll run reads that field.

• New joiner is assigned a location at onboarding; the correct state rule applies from month one.
• A transfer is entered once, with an effective date, and the deduction switches on that date in both states.
• An employee with no mapped location fails validation before payroll runs, rather than silently defaulting to head office.

That last behaviour is worth more than it sounds. Most multi-state errors are not wrong calculations; they are unassigned employees inheriting a default.

2. Slab Logic Is Configured Once, Centrally

State slab tables live in a maintained rules library rather than in a formula column. That gives you:

• Effective-dated slabs. When a state revises its structure from a given date, the new table applies from that date and historical months keep the old table. Retrospective recalculation of prior periods stops being a manual exercise.
• Correct base per state. Whether the band is read against gross, basic-plus-DA or a statutory definition is a state-level setting, not a per-employee habit.
• Special-month handling. The annual variation runs as a rule. Nobody has to remember February.
• Exemptions as attributes. An exempt employee is exempt because a flag with supporting documentation says so, and that flag is visible in a report.

3. Challan and Filing Tracking Stops Being Email

The remittance evidence chain — computed, paid, filed — is where audits actually get resolved, and it is usually the weakest link because it lives across a bank portal, a state website and someone's inbox.

An HRMS-based process gives you a per-state, per-month record with the challan number, date, amount and uploaded receipt attached to the payroll period it belongs to. Reconciliation becomes a report rather than an investigation, and the filing log sits next to the challan log rather than in a different system.

4. Reconciliation Runs Itself

The monthly question is always the same: does what we deducted equal what we remitted equal what we filed, per state? A system that holds all three can answer it as a standing report with variances flagged. A spreadsheet process answers it only when someone has time, which in practice means at year end, which in practice means never.

5. Employee-Facing Noise Disappears

Self-service payslips that show the deduction with the state name, plus a year-to-date figure, remove most of the questions before they are asked. Annual totals flow into the income tax computation and Form 16 without a separate extract.

6. Onboarding a New State Becomes a Checklist

When you hire in a new state, the sequence is: check applicability, obtain registrations, load the slab table, map the employee, add the state to the filing calendar. In a system, that is a configuration task with a visible completion state. On spreadsheets, it is an intention.

What Software Does Not Do

Be clear-eyed about the boundary. An HRMS applies rules accurately and keeps records reliably. It does not decide whether a single remote employee creates a taxable presence in a new state. It does not tell you whether your state has revised its slabs this week. It does not take a position on cross-state apportionment for a travelling employee.

Those are judgement calls, and they belong to your finance lead and your advisor. What the system does is make sure that once a judgement is made, it is applied consistently to every employee, every month, without depending on anyone's memory. That is the actual failure mode it fixes.

Frequently Asked Questions

Is professional tax the same across India?

No. It is levied by individual states and union territories under their own Acts, with their own slabs, forms, portals and calendars. Some states do not levy it at all. There is no single national rate, no national portal and no national return. Every state you employ in is a separate compliance track.

What is the difference between PTEC and PTRC?

PTEC (enrolment) covers the entity's own liability — the company, LLP or firm paying on its own account, usually an annual amount. PTRC (registration) covers the obligation to deduct from employees' salaries and remit to the state. Most employers with staff in a levying state need both. The names vary by state, but the two underlying concepts are consistent: pay for yourself, and deduct for your people.

Which state's rules apply to a fully remote employee?

There is no universal answer, and anyone who gives you a confident one-liner is oversimplifying. Work through it in order: does the employee's state levy the tax at all; does your entity have an establishment or place of business there; which office is the employee formally attached to and paid from; and has the state issued any clarification on remote work. Adopt a written policy, apply it consistently, and take advice where the position is genuinely unsettled.

What happens when an employee transfers between states mid-year?

Generally, you deduct under the origin state's rules up to the transfer date and the destination state's rules afterwards, remitting against the respective registrations. Watch three things: the effective date must match between HR records and payroll, any special-month variation may fall on one side of the transfer only, and the constitutional annual ceiling applies per person — an employee taxed in two states in one year may need specific treatment. That last point is an advisor question.

Do we have to file if we had no deduction in a month?

In most states, yes — if you hold an active deductor registration, a nil return is still required for periods with no liability. Dormant registrations in states where a branch has gone quiet are a common source of accumulated late-filing penalties. Either file the nil returns or formally surrender the registration; leaving it active and unfiled is the worst of the three options.

Can employees claim the deduction against income tax?

The Income-tax Act has historically allowed a deduction for taxes on employment borne by the employee, claimed against salary income and generally on a paid basis. Whether and how it is available depends on the tax regime the employee has chosen, and the rules in this area have changed in recent years. Confirm the current position for the relevant assessment year before configuring your TDS engine, and make sure the amounts flow correctly into Form 16.

How often do slabs change, and how do we keep up?

Changes typically arrive through a state budget or a standalone notification, and there is no coordinated announcement across states. Practical approach: check each state's commercial tax department portal quarterly and around state budget season, log the date you verified each state's table, and subscribe to updates from your payroll provider or advisor. Never assume a table you loaded eighteen months ago is still current.

What should we do if we discover we have been operating in a state without registering?

Quantify the exposure first — states, periods, headcount, approximate amount — then take state-specific advice before making any payment, because voluntary compliance or waiver mechanisms are sometimes available. Regularise the registration, then settle arrears against it, then document the whole remediation in a dated internal note. Finally, fix the upstream process so a new-state hire cannot be made without a registration check.

Conclusion

Professional tax is a small levy with an outsized ability to create problems, and the reason is structural rather than technical. It is not hard to calculate. It is hard to keep correct across states, across months and across the ordinary churn of joiners, leavers, transfers and remote hires — because there is no single rulebook, and the rules move independently in seventeen-odd places at once.

The employers who handle it well are not the ones with the cleverest spreadsheets. They are the ones who have turned it into a process: a state map that is reconciled to a registration map every quarter, slab tables with a recorded verification date, one owner per calendar item, a challan and filing log that lives in one place, and a written policy for the genuinely ambiguous cases so that nobody has to improvise on a deadline.

Three things to do this week, regardless of your size:

1. List every state where you have an employee working today — including remote hires and anyone at a coworking desk. Compare it to the list of states where you hold registrations.
2. Record, for each state on that list, the date you last verified the slab table against the state's portal. If you cannot, that is your answer about how current your configuration is.
3. Assign an owner to the monthly remit-and-file cycle and the quarterly state reconciliation. Not a team — a person.

If the reconciliation in step one produces a mismatch, do not panic; quantify it, take advice, and close it deliberately. Found-and-fixed is a materially better fact pattern than found-by-an-officer.

And if the underlying work — state mapping, slab logic, special-month rules, challan tracking, per-employee annual totals feeding the income tax computation — is currently held together by one analyst and a workbook, it is worth seeing what it looks like when the system carries it instead. CozyHR handles multi-state payroll for Indian teams with state-wise statutory configuration, automated deductions, payslip transparency and a compliance calendar that does not depend on anyone's memory. Take a look, run your own numbers through it, and see whether your quarterly reconciliation gets shorter.

---

This article is general information for Indian employers and is not legal, tax or accounting advice. All slabs, amounts, thresholds, months and calendar entries used above are illustrative examples included to explain mechanics, and are not statements of any state's current law. Professional tax provisions vary by state and are amended from time to time. Verify current requirements with the relevant state commercial tax or profession tax department, or with a qualified advisor, before acting.