What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
PF, ESI and professional tax are three different payroll deductions. They use different wage definitions, eligibility tests, rates, ceilings, authorities and filing records, so a reliable engine must calculate them as separate, versioned rules rather than applying one percentage to gross salary.
The most important current change is the announced increase in the EPFO mandatory-coverage wage ceiling from ₹15,000 to ₹25,000 per month effective 17 September 2026. Treat that as an effective-dated rule and verify the operative Gazette notification and EPFO implementation circular before deploying it. ESIC payroll material uses a ₹21,000 monthly wage ceiling, 3.25% employer and 0.75% employee rates, and an employee-share exemption when average daily wages are up to ₹176. Professional tax has no single national slab: it must be loaded by state or local authority, with its own slabs, exemptions, periodicity and effective dates.
As an Amazon Associate I earn from qualifying purchases.
What the payroll engine must calculate
A payroll run should produce three independent results for each employee and pay period:
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minute- PF (Employees’ Provident Fund): a retirement and social-security contribution administered through EPFO. The calculation normally starts with PF wages, commonly basic pay and dearness allowance where applicable, then applies the employee and employer rates to the wage base permitted by the active rule.
- ESI (Employees’ State Insurance): a social-insurance contribution administered by ESIC for covered employees. It has separate employee and employer shares, a wage ceiling and a special exemption from the employee share for low average daily wages.
- Professional tax: a salary-linked levy imposed under a state or local authority’s law. The amount depends on the employee’s jurisdiction, taxable wage definition, slab, payment frequency, exemptions and the version of the local notification.
Do not calculate any of these from an unqualified “gross salary” field. Keep component-level wages and eligibility inputs, then return an auditable breakdown containing the rule identifier, effective date, wage base, employee amount, employer amount, rounding result and filing status.
#1 Best Overall
PF calculation: wage base, ceiling and effective dates
How PF is calculated from basic salary
For an employee covered by the establishment and the applicable EPF scheme, determine PF wages from the statutory components. Basic pay and dearness allowance are the usual starting components; the engine should also represent any other component required by the governing scheme or establishment rule. Keep PF wages separate from total earnings because allowances and reimbursements do not automatically belong in the PF base.
The announced EPFO change matters when the rule caps contributions. For wages restricted to the statutory ceiling, the active ceiling is ₹15,000 per month before 17 September 2026 and ₹25,000 per month from 17 September 2026, subject to the final operative notification and scheme provisions. EPFO Imphal described the post-change calculation as ₹25,000 or actual salary/wages, whichever is lower, for employees whose contributions had been restricted to ₹15,000.
Do not infer that every employee earning above the ceiling is excluded. Establishment coverage, enrolment status, prior membership and any permitted higher-wage joint option must remain explicit inputs. An employee can have wages above the ceiling and still be covered, while another employee may require a different treatment under the applicable scheme.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPF rates and employer components
The rate must be configuration, not a hard-coded constant. A Government of Haryana release describes 12% employee and 13% employer contributions against the applicable ceiling. That figure is evidence for the cited Haryana release, not a universal instruction for every establishment. Your rule table should therefore hold the employee rate, employer rate, EPS allocation and employer administrative components independently, with the relevant establishment and scheme source recorded.
PF examples across the 2026 ceiling transition
Assume an enrolled employee has ₹30,000 of PF wages and the establishment caps contributions to the statutory ceiling. Under a pre-change rule, the wage base is min(₹30,000, ₹15,000) = ₹15,000. At a 12% employee rate, the employee share is ₹1,800. If the configured employer rate is 13%, the employer amount is ₹1,950.
Under a rule effective 17 September 2026, the capped wage base becomes min(₹30,000, ₹25,000) = ₹25,000. At the same 12% employee rate, the employee share is ₹3,000. At a configured 13% employer rate, the employer amount is ₹3,250. These amounts illustrate the arithmetic only; the engine must use the establishment’s active rate, EPS split and other statutory components.
A mid-month change needs an explicit payroll policy. Do not silently prorate or apply the new ceiling to the entire month unless the operative notification and your implementation rule require that treatment. Store the rule selected for each contribution period and preserve it on the payslip.
ESI calculation: coverage, wages and the employee-share exemption
Is ESI deducted from gross salary?
Not automatically. First test whether the employee and establishment are covered for the contribution period. Then calculate ESIC wages from the components included by the active ESIC rule. Gross salary can be a useful source total, but it is not a substitute for the statutory wage definition.
ESIC payroll material uses a ₹21,000 monthly wage ceiling. Because a tender document is not the same thing as a universal timeless rule, load the active ceiling from the current ESIC notification and retain the notification version in your configuration. If the employee’s applicable ESI wages exceed the ceiling, the covered wage base in a ceiling-capped rule is the lower of actual ESI wages and the configured ceiling.
ESI rates and the ₹176 threshold
ESIC guidance states that the contribution rate is 4% of wages: 3.25% is the employer share and 0.75% is the employee share. The same guidance provides an employee-share exemption when average daily wages are up to ₹176. The employer share still follows the applicable contribution rule; the exemption removes the employee deduction for the qualifying period.
The principal employer initially pays both shares to ESIC and may recover the employee share through payroll deduction for the relevant wage period. Model those as separate liabilities so the payment, recovery and reconciliation can be traced.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →ESI examples
For an employee with ₹18,000 of covered monthly wages and an average daily wage above ₹176, the employee share is ₹18,000 × 0.0075 = ₹135.00 and the employer share is ₹18,000 × 0.0325 = ₹585.00.
For an employee with ₹5,000 of covered wages whose configured average daily wage is ₹176 or less, the employee share is ₹0.00 under the exemption. The employer share is ₹5,000 × 0.0325 = ₹162.50. The engine should record the exemption decision and the average-daily-wage input rather than merely storing a zero amount.
Contribution periods can continue across a wage change, joiner or leaver event. Build the period logic from ESIC rules and your payroll calendar; do not assume that a single monthly snapshot answers every coverage question.
Professional tax: a jurisdiction-versioned deduction
Why there is no national professional-tax formula
Professional tax is imposed by the relevant state or local authority. Each jurisdiction can define its taxable salary components, monthly or other periodic slabs, annual maximum, exemptions, disability or age concessions, payment timing and effective dates. A national percentage or one nationwide table will produce incorrect deductions.
Store at least these fields for every professional-tax rule:
- State or municipal jurisdiction and the employer registration context.
- Effective-from and effective-to dates.
- Taxable-period wage definition and included components.
- Slab boundaries, amount and periodicity.
- Annual maximum levy where the local law has one.
- Exemptions and concessions, including disability or age conditions where applicable.
- Rule identifier and source notification.
The Income Tax Department treats professional tax as a salary deduction and explains the treatment where an employer pays it. Your payroll result should therefore distinguish an employee deduction from an employer-paid benefit or gross-up, then pass the correct amount to the salary statement and statutory return.
Professional-tax lookup flow
- Resolve the employee’s taxable jurisdiction from the governing state or local rule, not merely the office’s postal address.
- Calculate the taxable-period wages using that jurisdiction’s component definition.
- Apply exemptions and concessions before slab lookup.
- Find the slab in force on the payroll period’s effective date and apply its periodic amount.
- Enforce any annual maximum using year-to-date professional tax and the jurisdiction’s tax year.
- Return the deduction, rule identifier, effective date and calculation inputs for audit.
Use one rule model for all three calculations
A common rule object makes the engine explainable while allowing PF, ESI and professional tax to remain legally distinct. Represent each version with:
jurisdictioneffective_fromandeffective_towage_componentseligibility_predicateemployee_rateandemployer_rateceilingand whether to cap to itroundingsource_reference
Keep historical rules immutable. When a notification changes a ceiling or slab, insert a new version. Every payslip, ECR record and ESIC contribution record should retain the exact version used so a later update cannot rewrite a prior result.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Python implementation with Decimal arithmetic
Binary floating-point values can create paise-level discrepancies at statutory boundaries. Use Decimal, quantize monetary outputs explicitly and keep eligibility outside the arithmetic functions.
from dataclasses import dataclass
from decimal import Decimal, ROUND_HALF_UP
D = Decimal
def money(value: Decimal) -> Decimal:
return value.quantize(D('0.01'), rounding=ROUND_HALF_UP)
@dataclass(frozen=True)
class ContributionRule:
jurisdiction: str
effective_from: str
effective_to: str | None
employee_rate: Decimal
employer_rate: Decimal
ceiling: Decimal | None
cap_to_ceiling: bool
rounding: str
source_reference: str
def capped_wages(actual: Decimal, rule: ContributionRule) -> Decimal:
if rule.ceiling is None or not rule.cap_to_ceiling:
return actual
return min(actual, rule.ceiling)
def pf(employee, rule: ContributionRule) -> dict:
if not employee.pf_covered:
return {'eligible': False, 'wages': D('0.00'), 'employee': D('0.00'), 'employer': D('0.00')}
pf_wages = capped_wages(employee.pf_wages, rule)
employee_share = money(pf_wages * rule.employee_rate)
employer_share = money(pf_wages * rule.employer_rate)
return {
'eligible': True,
'wages': money(pf_wages),
'employee': employee_share,
'employer': employer_share,
'rule_reference': rule.source_reference,
}
def esi(employee, rule: ContributionRule) -> dict:
if not employee.esi_covered:
return {'eligible': False, 'wages': D('0.00'), 'employee': D('0.00'), 'employer': D('0.00')}
covered_wages = capped_wages(employee.esi_wages, rule)
exempt = employee.average_daily_wage <= D('176')
employee_share = D('0.00') if exempt else money(covered_wages * D('0.0075'))
employer_share = money(covered_wages * D('0.0325'))
return {
'eligible': True,
'wages': money(covered_wages),
'employee': employee_share,
'employer': employer_share,
'employee_share_exempt': exempt,
'rule_reference': rule.source_reference,
}
def professional_tax(employee, slab_table) -> dict:
slab = slab_table.lookup(
jurisdiction=employee.jurisdiction,
taxable_period_wages=employee.taxable_period_wages,
effective_date=employee.effective_date,
)
amount = money(slab.amount)
return {
'amount': amount,
'jurisdiction': employee.jurisdiction,
'rule_reference': slab.rule_reference,
}The functions intentionally do not decide whether an establishment is covered, whether an employee exercised a higher-wage option, which PF components include dearness allowance, or which professional-tax slab applies. Those are rule and master-data decisions. Keeping them outside arithmetic makes the result testable and lets a compliance reviewer inspect the inputs.
Selecting the correct rule by date
Use an effective-date resolver before calculating a contribution. It must reject overlapping versions and report an error when no rule exists.
def active_rule(rules, jurisdiction, effective_date):
matches = [
rule for rule in rules
if rule.jurisdiction == jurisdiction
and rule.effective_from <= effective_date
and (rule.effective_to is None or effective_date <= rule.effective_to)
]
if len(matches) != 1:
raise ValueError('expected exactly one active statutory rule')
return matches[0]For PF, load one rule ending before 17 September 2026 and another beginning on that date, then verify both against the final EPFO communication. For ESI, keep the ₹21,000 figure as a configured value only when it is supported by the active notification used by your organisation. For professional tax, select by jurisdiction and date on every payroll close.
Comparison of PF, ESI and professional tax
| Dimension | PF | ESI | Professional tax |
|---|---|---|---|
| Authority | EPFO and the applicable EPF schemes | ESIC | State or municipal authority |
| Eligibility | Establishment coverage, enrolment and scheme conditions; do not infer exclusion solely from salary | Covered establishment and employee, contribution-period conditions and wage ceiling | Employee’s jurisdiction, taxable status and local exemptions |
| Wage definition | PF wages, commonly basic pay and dearness allowance where applicable | ESI wages under the active ESIC rule | Components specified by the local professional-tax law |
| Ceiling | ₹15,000 before 17 September 2026; announced ₹25,000 from that date, subject to operative notification and scheme rules | ₹21,000 in ESIC payroll material; source the active notification | Varies by jurisdiction; may have an annual maximum |
| Employee rate | Configured by scheme and establishment rule; a Haryana release describes 12% | 0.75% | Slab amount, not a national percentage |
| Employer rate | Configured by scheme and establishment rule; a Haryana release describes 13% | 3.25% | Usually a payroll deduction or employer-paid amount according to local treatment |
| Special exemption | Higher-wage options and scheme-specific conditions must be represented | Employee share is exempt at average daily wages up to ₹176 | Local exemptions and concessions, such as qualifying age or disability provisions |
| Output | Employee and employer contribution, EPS and administrative components, ECR/challan data | Employee and employer shares, contribution-period record and ESIC payment data | Deduction, jurisdiction, slab, rule version and local return data |
Rounding, boundaries and payroll events
Round only at the statutory output
Keep intermediate values as Decimal. Quantize the employee and employer amounts to two decimal places using the rounding policy in the rule. Do not round the wage base before applying the rate unless the governing rule says to do so. Store both the unrounded calculation and the posted amount when your audit requirements call for it.
Test ceiling boundaries
- PF wages exactly ₹15,000 under the pre-change rule.
- PF wages exactly ₹25,000 under the post-change rule.
- PF wages one rupee below and above each ceiling.
- ESI wages exactly ₹21,000 and just above it, using the active notification.
- Average daily wages exactly ₹176, just below and just above.
- Professional-tax wages on every slab boundary and annual maximum.
Test employment events
- Joiners and leavers whose service covers only part of a contribution period.
- Unpaid leave and zero-wage periods.
- Mid-period salary changes and the 17 September 2026 PF effective-date transition.
- Negative adjustments, reversals and recovery of an over-deduction.
- Idempotent reruns: recalculating the same payroll input must not duplicate a liability or filing line.
Filing and reconciliation records
EPFO provides employer registration, monthly ECR/challan submission and online payment services. ESIC guidance describes online contribution handling and payment within 15 days after the month in which the contribution falls due. A production engine should not stop at a payslip number. Create first-class records for the filing period, employee lines, total employee share, total employer share, challan or filing ID, payment date, bank reference and reconciliation status.
Reconcile three totals separately: the payroll deductions posted to employee ledgers, the employer liability booked in accounting and the amount submitted in the statutory file. A mismatch should identify the employee, rule version, wage base and rounding difference instead of forcing an operator to compare an opaque total.
Operational safeguards before production
- Validate master data: establishment coverage, EPFO enrolment, ESI insurance details, jurisdiction, age or disability flags and wage components must be complete.
- Load dated rules: enter the pre- and post-17 September 2026 PF versions, the active ESIC ceiling and every professional-tax jurisdiction used by the workforce.
- Attach source references: store the notification, circular or authority release with each rule and require a reviewer for changes.
- Run golden cases: include the numerical examples and all boundary tests in automated tests.
- Compare parallel output: for a controlled payroll, compare employee-level results with an approved statutory calculation before enabling deductions.
- Freeze payslip evidence: write the rule ID, effective date, wage components, rates, ceiling, exemption decision and rounded amounts to an immutable payroll result.
- Monitor changes: the 2026 PF ceiling announcement is recent; recheck the operative Gazette and EPFO implementation circular before rollout. Recheck ESIC ceilings and local professional-tax notifications whenever an authority publishes a change.
Common failure modes and fixes
Applying a percentage to gross salary
Symptom: deductions rise whenever a reimbursement or excluded allowance is added. Fix: maintain separate PF, ESI and professional-tax wage-component maps and calculate each base independently.
Free tools Windows power users keep installed
One-click scans. No signup required.
Hard-coding ₹15,000 or ₹25,000 forever
Symptom: historical payslips change after a configuration update, or September 2026 payroll applies one ceiling to the entire period without a documented policy. Fix: use immutable effective-dated rules, resolve by period date and preserve the selected rule on every result.
Excluding every employee above a ceiling
Symptom: a covered employee disappears from ECR or ESIC output after a salary increase. Fix: keep establishment coverage, enrolment and higher-wage status as explicit eligibility fields; ceiling and eligibility are different decisions.
Charging the ESI employee share at every wage level
Symptom: an employee with average daily wages of ₹176 or less is deducted 0.75%. Fix: calculate and store the average-daily-wage test, then apply the exemption to the employee share when the active ESIC rule qualifies it.
Using one professional-tax table nationwide
Symptom: employees in different states receive the same slab amount. Fix: key the table by jurisdiction, periodicity and effective date, and include the local notification reference in the result.
Rounding with binary floats
Symptom: one-paise differences appear between payroll, ledger and challan totals. Fix: use Decimal, an explicit rounding mode and deterministic aggregation tests.
What a compliant result should look like
For each employee and period, return a component breakdown rather than one combined “statutory deduction” number:
- PF: eligibility decision, PF wage base, ceiling and cap decision, employee share, employer share, EPS allocation, administrative component and rule reference.
- ESI: eligibility decision, ESI wage base, ceiling, average daily wage, employee-share exemption decision, employee share, employer share and rule reference.
- Professional tax: jurisdiction, taxable wages, exemptions, slab and periodicity, amount, year-to-date maximum check and rule reference.
- Operations: payroll run ID, filing period, ECR or ESIC line identifier, challan total, payment date and reconciliation state.
This structure answers why a deduction changed: the reviewer can see whether the cause was a wage-component change, a ceiling transition, a coverage decision, an exemption, a jurisdictional slab or a rounding policy.
Quick Recap
Final implementation checklist
- Use separate PF, ESI and professional-tax calculators.
- Use
Decimaland explicit paise rounding. - Resolve every rule by jurisdiction and effective date.
- Implement the announced PF ceiling transition from ₹15,000 to ₹25,000 on 17 September 2026 only after verifying the operative EPFO material.
- Configure ESI at 3.25% employer and 0.75% employee, apply the ₹176 average-daily-wage exemption, and source the current wage ceiling from ESIC.
- Never hard-code a nationwide professional-tax rate; load local slabs, exemptions, periodicity and annual limits.
- Preserve rule versions and component-level evidence on every payslip.
- Separate calculation from ECR, ESIC and local-tax filing adapters.
- Test boundaries, mid-period events, negative adjustments and idempotent reruns.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
