Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
A six-state employer with 920 employees runs PT cycles in parallel across Karnataka, Maharashtra, Gujarat, West Bengal, Tamil Nadu, and Telangana, each with different slabs, different cut-offs, and different portals. Without state-wise reconciliation, employees get assigned to the wrong state on transfer, the wrong slab is applied, and one state's deposit gets missed without anyone noticing until the inspection notice arrives.
Carry a per-employee state-of-work field on the payroll register every month. Compute PT per employee using the slab schedule of the assigned state. Aggregate per-state totals and reconcile against the per-state deposit. Surface variances per state per month — missing state-of-work value, slab-master gap, deposit-not-made, deposit-amount-mismatch.
Per-employee state-of-work master, per-state slab schedule (Karnataka, Maharashtra, Gujarat, West Bengal, Tamil Nadu, Telangana, and any others where the employer is registered), per-state cut-off calendar, deposit reference master, and a per-state-per-month reconciliation MIS.
Clean state-wise PT filings, every employee assigned to the correct state, every slab applied correctly, every state's deposit made on time, and a defensible audit trail showing per-employee PT contribution from payroll register through state-level deposit.
Professional tax looks like a small statutory obligation per employee — at most ₹2,500 a year per person under the constitutional cap — but a multi-state Indian employer runs as many parallel PT cycles as the number of PT-levying states it operates in, each with its own slabs, cut-offs, and portals. The reconciliation discipline is not difficult in principle, but it falls apart quickly when the state-of-work field on the payroll register is unreliable or the per-state cut-off calendar is not encoded.
What State-wise PT Reconciliation Involves
PT reconciliation is the monthly process of computing per-employee PT using the slab schedule of the state in which the employee is assigned for that month, aggregating per state, depositing to the state’s commercial taxes department within the state-specific cut-off, and reconciling the deposit against the computed liability.
The state-of-work field on the payroll register is the controlling input. For employees in a single fixed state, it is static. For employees on transfer or temporary assignment, it is set by policy — typically the principal state of work for the month. Without a reliable state-of-work field, every other step in the reconciliation runs on bad input.
Per-State Slab Reference
The table below summarises the current slab structure for the six states the worked example covers. Exact thresholds and amounts should be confirmed against the latest notification from each state’s commercial taxes department before configuration.
| State | Slab Structure (illustrative) | Annual Cap | Filing Cut-off |
|---|---|---|---|
| Karnataka | ₹200 per month above the threshold gross salary | ₹2,500 | 20th of following month |
| Maharashtra | Multi-slab from ₹175 to ₹300 monthly, higher rate in February | ₹2,500 | End of following month |
| Gujarat | ₹200 per month above the threshold gross salary | ₹2,500 | 15th of following month |
| West Bengal | ₹110 to ₹200 per month across slabs | ₹2,500 | 21st of following month |
| Tamil Nadu | Six-monthly cycle, slab-based | ₹2,500 | Half-yearly filing |
| Telangana | Multi-slab from ₹150 to ₹200 monthly | ₹2,500 | 10th of following month |
The slab amounts above are illustrative of the structure; configure each state from its current notification.
The Monthly PT Reconciliation Cycle
Step 1: Payroll Register Close
The payroll register closes at the end of the salary cycle, carrying per-employee gross wages and the controlling state-of-work field. The reconciliation engine validates that every active employee has a state-of-work value populated.
Step 2: Per-Employee PT Computation
For each employee, the engine looks up the slab schedule of the assigned state and computes the PT amount for the month. The computation is written to a reconciliation row per employee per state per month.
Step 3: Per-State Aggregation
The per-employee rows are aggregated by state. The aggregate is the employer’s PT liability for the state for the month.
Step 4: Per-State Deposit
The deposit is made to the state commercial taxes department within the state-specific cut-off. Each state has its own deposit channel — typically a portal challan generation followed by a NEFT or RTGS deposit.
Step 5: Reconciliation MIS
The reconciliation engine produces a per-state-per-month MIS showing computed liability, deposit reference, deposit date, and variance. Open variances are cleared the same week.
Worked Example: Six-State Employer with 920 Employees
An IT services company runs 920 employees across six PT-levying states — 380 in Karnataka (Bengaluru), 220 in Maharashtra (Mumbai and Pune), 110 in Gujarat (Ahmedabad), 95 in Tamil Nadu (Chennai), 75 in Telangana (Hyderabad), and 40 in West Bengal (Kolkata).
Monthly PT liability across the six states aggregates to approximately ₹1.6 lakh, with significant per-state variation reflecting the different slab structures.
Before state-wise reconciliation: the payroll team computed PT in a single spreadsheet by applying an average per-employee amount and depositing in Karnataka (the registered head-office state) on the 20th. The Maharashtra, Gujarat, West Bengal, Tamil Nadu, and Telangana liabilities were either underpaid or paid late to those states’ departments. The first inspection in Maharashtra found 22 months of misallocated PT — Maharashtra employees’ PT had been deposited in Karnataka, not Maharashtra. The state imposed the underpaid PT (substantial), interest, and penalty for the lookback period.
After state-wise reconciliation: the payroll register carries a state-of-work field per employee per month. The reconciliation engine applies the correct slab per state, aggregates per state, and produces six independent deposit instructions to the six state departments. Each deposit is made within the state-specific cut-off. The reconciliation MIS shows per-state per-month status and any variances are cleared the same week. The annual inspection burden is per-state per-year, but each state’s records reconcile cleanly.
Want to estimate the cost of misallocated PT across multiple states for your own employee base? Run the three-way match exception cost calculator — substitute exception count and per-exception cost with per-state mis-allocation count and per-state penalty exposure.
Multi-State Employee Handling
Employees who work in more than one state in a single month are the hardest case. Three patterns are common.
Permanent transfer mid-month: the employee moved from state A to state B on the 15th. Most employers apply state A’s PT for the half-month worked in state A and state B’s PT for the half-month worked in state B, prorated by working days. Some employers apply the full month’s PT to the state where the employee was based on the salary cut-off date, accepting the small misallocation in exchange for simpler computation. The policy must be documented and consistently applied.
Temporary assignment: the employee’s base location is state A but they spent three weeks of the month at a client site in state B. The principal state of work remains state A; PT is computed and deposited in state A. The reconciliation engine should not switch state on temporary assignment unless the employer’s policy explicitly says so.
Work-from-home from a non-base state: the employee’s registered base is state A but they are working from state B for personal reasons. Most employers continue to apply state A PT because the employment contract is registered there. The legal position is occasionally disputed, but for reconciliation, the registered base state is the controlling field.
Interplay with EPF and ESI
PT, EPF, and ESI all run on the same payroll register. The reconciliation discipline benefits from running them together — one engine, one register, three obligations per employee per month, three deposit cycles per state or central authority. Running them in separate spreadsheets multiplies the data-quality risk because each spreadsheet needs its own copy of the payroll register and they drift apart.
EPF and ESI are central obligations — single establishment code, single cut-off (15th of following month), single portal each. PT is decentralised — one state at a time, one cut-off at a time, one portal at a time. The engine should handle both topologies on the same per-employee reconciliation row.
State Registration Hygiene
Before reconciliation can run cleanly, the employer’s PT registration in every state where it has employees must be current. A common failure pattern: the employer hired in a new state, payroll started processing employees there, but the employer never registered for PT in that state. The reconciliation engine computes a liability but the employer cannot deposit because no registration exists. The exposure builds month over month until an inspection surfaces it.
The MIS should explicitly flag any state where employees exist but no PT registration is configured. This is a state-master configuration issue, not a reconciliation issue, but the reconciliation engine is well placed to surface it.
Common Pitfalls
Single-state deposit: depositing all PT in the head-office state, which under-deposits in every other state. The misallocation surfaces years later in an inspection.
Stale state-of-work field: not updating the state assignment when an employee transfers, which causes the wrong slab and the wrong state deposit.
Missing state registrations: hiring in a state without registering for PT, then accumulating an undepositable liability.
Treating PT as quarterly because Maharashtra files quarterly returns: most states are monthly. The deposit calendar must be encoded per state.
Closing Note
State-wise PT reconciliation is a discipline of state count multiplication, not amount size. The per-employee per-month amounts are small; the consequences of misallocation across states are not, because every state’s commercial taxes department audits independently and the lookback period in inspections is typically multi-year. A 920-employee employer in six states with a per-employee state-of-work field and a per-state cut-off calendar runs the cycle cleanly. Without those two foundations, the cycle accumulates an undisclosed liability that surfaces during inspection at a cost an order of magnitude larger than the deposit itself.