Why Your Payroll Is Probably Wrong (And How to Fix It)

After auditing payroll processes at more than 20 Pakistani SMEs over three years, I've found that virtually every company has at least one systemic payroll error that they don't know about. Not occasional mistakes — structural miscalculations that repeat every month, sometimes for years, creating cumulative compliance exposure or overcharging employees.

The uncomfortable truth: most of these errors are invisible. The salary slip looks right. The bank transfer goes through. Employees don't complain. And then an FBR notice arrives, or an EOBI audit request, or a Labour Department inspection — and the accumulated error becomes a real liability.

Here are the six most common payroll errors in Pakistani companies, what they cost, and how to fix each one permanently.

Error 1: EOBI Calculated on Actual Salary Instead of Minimum Wage

What's happening: The HR system calculates EOBI employee deduction as 1% of the employee's gross salary. For an employee earning PKR 80,000, the deduction is PKR 800/month instead of the correct PKR 370/month (1% of PKR 37,000 statutory minimum wage).

The impact: The employee is being overcharged by PKR 430/month — PKR 5,160/year. Across 30 employees, that's PKR 154,800/year in excess deductions. If discovered in a compliance audit or employee grievance, the employer must repay the excess with interest.

Conversely, some systems calculate the employer's 5% on actual salary, resulting in EOBI overpayment (PKR 4,000/month employer contribution for an PKR 80,000 employee instead of PKR 1,850). This excess cannot be recovered from EOBI.

The fix: Lock EOBI calculations to the statutory minimum wage, not actual salary. This is a configuration change in your payroll system, but verify it by manually cross-checking three salary slips next payroll cycle.

Check now: Pick three salary slips from last month. Multiply the "EOBI Employee" deduction by 100. If the result is not approximately PKR 37,000 (give or take small rounding), the calculation is wrong.

Error 2: PESSI/SESSI Contributions Skipped for Above-Ceiling Employees

What's happening: HR team believes that once an employee earns above the PESSI/SESSI insurable wage ceiling (PKR 30,000), they don't need to be enrolled or contributions paid.

Why this is wrong: PESSI and SESSI enrollment is based on employment status, not salary. Employees earning above PKR 30,000 are still enrolled — you just calculate their contribution on the ceiling (PKR 30,000) rather than their actual salary. An employee earning PKR 120,000 costs you PKR 1,800/month in PESSI contributions, same as an employee earning PKR 35,000.

The impact: Employees not enrolled in PESSI/SESSI have no access to social security medical benefits. If an unenrolled employee has a medical emergency or workplace injury, the employer faces liability under the Social Security Ordinance. Additionally, back-contributions plus 1% monthly penalties will be assessed from the employee's hiring date.

The fix: Enroll every employee meeting the tenure requirement (6+ months) regardless of salary level. Calculate PESSI/SESSI contributions at 6% of actual wages for employees below PKR 30,000, and at 6% of PKR 30,000 (= PKR 1,800) for everyone above.

Error 3: Income Tax Calculated Annually but Deducted Unevenly

What's happening: The tax calculation is correct on an annual basis, but the monthly deduction is inconsistent because the system calculates fresh each month rather than annualizing and spreading evenly.

Example: An employee with annual taxable income of PKR 3,600,000 (PKR 300,000/month) owes approximately PKR 360,000 in annual income tax (under 2026 FBR slabs). The correct monthly deduction is PKR 30,000. But if the system recalculates from scratch each month without annualization, months with bonuses or irregular payments generate wildly different deductions — sometimes PKR 45,000, sometimes PKR 18,000.

The employee experience: Income tax deductions that vary significantly month to month confuse employees, generate HR queries, and reduce trust in the payroll system's accuracy even when the annual total is technically correct.

The fix: Annualise income tax calculation. Estimate full-year taxable income (including projected bonuses), calculate the annual tax liability, then divide by 12 for a consistent monthly deduction. Reconcile at year-end. This is standard practice per FBR guidelines.

The bonus trap: When a bonus is paid, some systems add the full bonus amount to the monthly calculation and charge income tax as if the employee earns at that elevated rate year-round. This over-deducts in bonus months and under-deducts in normal months. Spread the bonus over the remaining months of the tax year to avoid spikes.

Error 4: Gratuity Not Provisioned (Time Bomb on the Balance Sheet)

What's happening: The company pays gratuity when employees resign or are terminated but does not accrue a monthly provision. Gratuity is treated as a cash-out event rather than an ongoing payroll expense.

Why this is a problem: Under the West Pakistan Industrial and Commercial Employment (Standing Orders) Ordinance 1968, every permanent employee accumulates one month's last drawn basic salary per year of service. A company with 40 employees, average basic salary PKR 45,000, average tenure 3 years, has a gratuity liability of approximately PKR 5,400,000 sitting off the balance sheet.

When three senior employees resign in one quarter, the company suddenly needs PKR 1,350,000 in cash that hasn't been provisioned. This is a real cash flow crisis that happens to Pakistani companies regularly.

The fix: Accrue gratuity monthly at 1/12th of current month's basic salary per employee. Record it as a payroll expense and a liability provision. This means your financial statements reflect the actual cost of your workforce, and you're never surprised by a gratuity payout.

Error 5: Mid-Month Joiners and Leavers Calculated Incorrectly

What's happening: When an employee joins on the 15th of the month or resigns effective the 20th, the pro-rated salary is calculated incorrectly because the system uses a fixed 30-day month denominator regardless of actual days.

Example: March has 31 days. An employee with a PKR 60,000 salary joins on March 16. The correct pro-rated salary is PKR 60,000 × (16 days / 31 days) = PKR 30,968. If the system divides by 30: PKR 60,000 × (16 / 30) = PKR 32,000 — an overpayment of PKR 1,032.

This is a small error per employee, but it systematically overpays joiners and underpays leavers (or vice versa, depending on which way the rounding goes). Across 15–20 joiners and leavers per year, the accumulated error is material.

The fix: Pro-rate based on actual calendar days in the month, not a fixed 30-day denominator. Most modern payroll systems have a setting for this — verify which method your system uses.

The additional complexity: Pro-rating affects not just gross salary but also all contributions (EOBI, PESSI) and allowances. Ensure the pro-rating is applied consistently across all payroll components, not just to basic salary.

Error 6: Leave Encashment Not Taxed Correctly

What's happening: Leave encashment is paid out when an employee leaves or during annual settlement, and it is treated as a tax-free payment — because someone said "leave encashment is exempt" without checking the specifics.

The actual rule: Leave encashment paid at the time of resignation, retirement, or termination is exempt from income tax per the Income Tax Ordinance 2001. However, leave encashment paid during employment (as an annual settlement while the employee remains employed) is fully taxable as salary income.

Many HR teams apply the exemption to all leave encashment payments, creating an FBR compliance risk for regular annual leave payouts.

The fix: Apply the income tax exemption only to leave encashment paid on termination of employment. For leave encashment paid to current employees (annual settlement), include it in taxable salary for that month's income tax calculation.

The Audit Exercise

You can identify whether you have any of these errors without waiting for an external audit. Set aside two hours and do the following:

Step 1: Pull last month's payroll run for 5 employees — ideally two junior staff, two senior staff (above PKR 30,000), and one mid-month joiner or leaver.

Step 2: Manually calculate for each:

• EOBI employee deduction (should be PKR 370)
• EOBI employer contribution (should be PKR 1,850)
• PESSI contribution (should be PKR 1,800 or 6% of actual salary if below ceiling)
• Income tax (compare to FBR tax calculator at fbr.gov.pk)
• Pro-rated salary for any partial months (actual calendar days)

Step 3: Compare to payroll register. Any differences above PKR 50 deserve investigation.

This exercise takes longer with a manual system. With a properly configured HRMS, the system does it automatically and flags anomalies before the payroll is finalised.

The Cost of Getting It Right vs. Wrong

Frequently Asked Questions

Q: If I've been calculating EOBI incorrectly for two years, am I liable for back-payments? A: Yes, EOBI can assess back-contributions for up to 5 years with 1% monthly compound penalties. Voluntary disclosure (approaching EOBI before they find the error) typically results in more favourable settlement terms than waiting for an inspection.

Q: Should I run a payroll audit internally or hire an external consultant? A: Internal audit first. The six errors described here are findable with one or two hours of manual cross-checking. If you find discrepancies, bring in an HR consultant or CA who specialises in payroll compliance to assess the full exposure.

Q: Do I need to notify employees if I've been under-deducting income tax? A: Yes. If income tax has been under-withheld, the employer is responsible for remitting the correct amount to FBR. If the amount is significant, you should discuss with employees before making large retroactive deductions — they may have a right to understand why their net salary is suddenly lower.

Q: How often should payroll be audited? A: A compliance cross-check (EOBI, PESSI, tax) quarterly. A full pro-rating and calculation audit semi-annually. A full payroll system audit annually when any law changes (Finance Act, minimum wage revision).

Building a Payroll System That Doesn't Require Monthly Vigilance

Every one of these errors is preventable through proper system configuration. The goal is a payroll run that HR can finalize in under two hours, confident that all calculations are correct, all compliance contributions are accurate, and all exceptions (joiners, leavers, bonuses, advances) are handled without manual intervention.

That's achievable — but only with a payroll module built specifically for Pakistani compliance requirements.

See Workflow Engine's payroll module handle EOBI, PESSI, and FBR tax correctly — book a demo.