Payroll & Compliance 10 min read

HR Compliance in Pakistan: An Employer Control Guide

A practical control framework for HR and finance teams managing federal tax duties and provincial employment obligations.

Pakistani HR professionals reviewing HR and payroll software on a laptop facing them in an office
On This Page
  1. 01What Does HR Compliance in Pakistan Cover?
  2. 02How Should Payroll Deductions Be Checked?
  3. 03Which Employment Records Should Employers Maintain?
  4. 04How Can HR And Finance Run A Monthly Review?
  5. 05Summary
  6. 06Frequently Asked Questions

Quick Answer

HR compliance in Pakistan means meeting the employment, payroll, tax and social protection obligations that apply to your establishment and workforce. Start by identifying the relevant province and employee coverage, then document terms, validate deductions and contributions, maintain supporting records and assign responsibility for reviewing legal changes.

Key Takeaways

  • Coverage Comes First. Not every law applies to every establishment or employee in the same way.
  • Separate The Authorities. FBR withholding, EOBI and provincial social security need distinct checks.
  • Keep Evidence. Approved payroll inputs, calculations and payment receipts should reconcile.
  • Software Needs Oversight. Configuration supports compliance; it does not replace legal review.

What Does HR Compliance in Pakistan Cover?

HR compliance covers the rules applicable to an employment relationship, from appointment through separation. The starting point is coverage, not a universal checklist: establishment type, province, worker classification and the relevant legislation determine which duties your HR and finance teams must meet.

For a multi-location employer, organise the register around workplaces rather than a single head-office policy. Give each branch an entry showing its activity, address, workforce categories and responsible manager. Record the law or notification reviewed, the conclusion reached and the person who approved it. If an employee transfers between locations, flag the move for an applicability review instead of changing only the cost centre. This makes the register useful during actual personnel decisions, not merely during an annual documentation exercise.

Separate a legal requirement from a contractual promise and an internal operating preference. For example, an employer may offer a benefit through its appointment terms without that benefit being the statutory minimum for every employee. Mark those different foundations in the policy register. Otherwise a manager might remove a contractual benefit because a statutory checklist does not mention it, or assume a generous company policy resolves every legal obligation. Where the interaction is unclear, seek employment-law advice before issuing revised terms.

Use official publications as the source trail: FBR for income tax, EOBI for its scheme, and the relevant provincial department or institution for local requirements. The Punjab Labour and Human Resource Department is a starting point for Punjab research, not authority for every province. Save the document title, issuing authority, publication date and effective date in the register. A search result, consultant summary or payroll setting can help identify a question, but should not be the final evidence for a legal conclusion.

Build an obligations register for each operating location. A Lahore office and a Karachi operation may need different provincial labour and social security assessments. Do not assume that incorporation alone determines the employment law applicable to every worker.

  • Record establishment type, operating province and employee categories.
  • Identify applicable appointment terms, working-time, leave and wage requirements.
  • Check EOBI and provincial social security coverage separately.
  • Assign an owner and an official source to each obligation.

Use Payroll Compliance to review the calculation workflow after confirming the legal basis. Keep the authority’s current guidance beside the approved configuration.

The tax computation screen separates taxable and non-taxable earnings for review.

How Should Payroll Deductions Be Checked?

Payroll controls should connect each deduction or contribution to a verified legal basis, an approved calculation and evidence of payment. Review salary tax separately from pension and provincial social security obligations, because their coverage, calculation bases and administrative requirements are not interchangeable.

For salary tax, build a bridge from the employee record to the annual calculation. Review which earnings and benefits have entered the taxable-pay assessment, how expected annual earnings were established and how tax already deducted is reflected. A bonus, retrospective increase or mid-year joining can change the calculation inputs. Ask the reviewer to explain the movement against the previous period, not simply confirm that a deduction appears on the payslip. Keep the approved explanation with the payroll working papers.

Give minimum-wage reviews their own worksheet rather than burying them inside tax setup. Identify the applicable notification, its coverage, the wage period and the components being compared. Do not assume that a package above a headline amount settles the question if the applicable wage definition has not been checked. Review changes in hours, worker category and location alongside salary changes. Any proposed recovery or other deduction should also have a documented basis; a manager’s request alone is not a legal assessment.

For EOBI and provincial social security, maintain separate employee coverage lists and reconcile them to the payroll population. Investigate people present on one list but absent from another: the difference might reflect coverage, missing registration information or an administrative error. Record the reason rather than forcing the totals to match. Match each institution’s payment evidence to the relevant period and calculation schedule. A bank debit without an identifiable allocation does not explain which employees or liabilities the payment was intended to cover.

FBR’s Income Tax Ordinance, 2001 is the starting point for salary withholding obligations. Check the current Finance Act, applicable rules and FBR instructions before approving tax-year settings, deposit dates or statement requirements. Do not copy filing labels or deadlines from an older article.

EOBI administers old-age benefits, while PESSI and SESSI administer provincial social security schemes. Confirm coverage and check the current notified figure for the relevant contribution basis before calculation. Keep employee eligibility changes and payment receipts with the monthly reconciliation.

The EOBI registration guide provides a separate registration workflow. It should sit alongside, not replace, the employer’s review of current EOBI instructions.

Review contribution configuration against current EOBI requirements before payroll.

Which Employment Records Should Employers Maintain?

Maintain a traceable record of employment terms, attendance, leave, pay changes and separation decisions. The required documents and retention periods depend on the applicable law, but a consistent record structure helps HR explain decisions and finance reconcile the amounts processed each month.

An employee file should tell a chronological story. Connect the appointment document to subsequent salary revisions, role changes, location transfers and acknowledged policy changes. Maintain an index so reviewers can distinguish the operative terms from superseded drafts. Collect identity and registration details through an authorised process, restrict access to those who need them and avoid circulating full employee files in routine payroll emails. These are recommended handling controls, not a claim that one retention or privacy rule covers every Pakistani workplace.

Attendance records need an exception trail as well as a total. A missing punch, approved absence and unpaid absence should not become interchangeable payroll inputs. Retain the original entry, correction request, manager decision and resulting pay treatment. For overtime, check both the applicable legal framework and the evidence that the work was authorised and performed. Do not silently convert all additional hours into a flat allowance merely because that is easier to enter in payroll.

At separation, prepare an entitlement worksheet before agreeing a net settlement. Identify the employee category, relevant terms, last working date, outstanding earnings and the basis for each proposed benefit or deduction. Reconcile leave balances and advances against their underlying records, and identify disputed amounts separately from agreed figures. Keep asset-return administration visible without assuming it automatically permits withholding any amount. If notice, gratuity or provident-fund treatment is uncertain, resolve that specific issue with qualified advice rather than applying a precedent from an unrelated employee.

Practical HR Compliance Evidence Register
Practical HR Compliance Evidence Register
Control AreaEvidence To ReviewResponsible Function
Employment termsAppointment terms and approved changesHR
Time and leaveAttendance corrections and leave decisionsHR and managers
PayrollApproved inputs, calculation and payment evidenceFinance
SeparationApplicable entitlements and settlement approvalHR and finance

Review leave and overtime against the applicable provincial framework rather than importing one company-wide statutory entitlement. Confirm notice, gratuity, provident fund and leave encashment treatment before preparing a final settlement. Avoid treating every employee category as legally identical.

Review the applicable provincial social security configuration separately from EOBI.

How Can HR And Finance Run A Monthly Review?

A monthly review should confirm employee changes, approved time records, statutory calculations and payment evidence before the payroll period is closed. Assign named reviewers and keep unresolved items visible, so an incorrect configuration is investigated rather than silently carried into the next pay run.

Use an exception meeting to focus the monthly review. HR should bring unresolved joiner documentation, transfers, attendance corrections and exit cases; finance should bring unexplained calculation movements and unmatched payments. Give each exception a named owner and a decision date. Distinguish a missing document from a disputed legal interpretation, because the second may need external advice rather than another reminder email. Record whether an item blocks approval or can proceed under a documented, authorised treatment.

After payment, assemble a period-close evidence pack containing the approved employee population, change log, payroll summary, authority-specific schedules and payment or submission acknowledgements. Reconcile rejected or returned payments instead of treating a submitted instruction as proof of completion. Keep later corrections linked to the original period so the next reviewer can follow both versions. This also helps HR answer an employee query without reconstructing the calculation from messages spread across several inboxes.

Test legal changes through a controlled revision process. When an official notification is identified, establish which locations, employees and periods it affects before editing a live setting. Have a second reviewer compare sample calculations under the old and proposed treatment. Record the reason for any retrospective adjustment and explain the resulting payslip movement to affected employees. A change log should state what changed, who approved it and which evidence supports it; an overwritten percentage field supplies none of that context.

  • Reconcile joiners, leavers and pay changes against approved records.
  • Resolve attendance and leave exceptions before payroll approval.
  • Check tax, pension and social security settings against current authority guidance.
  • Reconcile approved payroll with payment and filing evidence.
  • Log legal changes with their effective dates and configuration decisions.

PayPeople’s payroll compliance page describes FBR tax computation, EOBI contribution setup and provincial social security calculations. Employers should still review the settings and employee coverage. An automated calculation is only useful when the underlying inputs and legal interpretation are correct.

Summary

Compliance starts with knowing which rules apply, then maintaining evidence that the business followed them. Give HR and finance clear ownership, validate changes against official sources and treat software as a controlled workflow rather than a legal guarantee.

Next step: see how this works in PayPeople Payroll Compliance.

Frequently Asked Questions

Does Every Labour Law Apply To Every Employer?

No. Coverage depends on the statute, establishment type, operating location and employee category. Start with an applicability review rather than assuming that every business follows exactly the same obligations. Record the basis for each decision, and obtain qualified advice where coverage or worker classification is uncertain.

Are Provincial Labour Rules The Same Across Pakistan?

No. Employers should check the applicable provincial framework for each establishment and workforce. A policy used in Punjab should not automatically be copied into Sindh without review. Maintain a location-based register of requirements, official references and approved policy differences so managers apply the correct rules consistently.

How Does Salary Tax Fit Into HR Compliance?

Salary withholding is a separate payroll responsibility under the FBR framework. HR supplies accurate employee and earnings data, while the responsible payroll or finance team checks the computation and current filing requirements. Use current FBR legislation and guidance rather than assuming that last year’s tax settings remain suitable.

Are EOBI And Provincial Social Security The Same?

No. EOBI concerns old-age benefits, while provincial social security institutions operate separate schemes with their own coverage and administrative requirements. Review each obligation independently. Keep registrations, employee eligibility records, calculations and payment evidence organised so a reconciliation does not confuse one institution’s contribution with another institution’s requirement.

Does Payroll Software Make A Business Compliant?

Software can support calculations and record keeping, but it cannot determine every legal question for an employer. Coverage, employee classification and policy interpretation still require review. Confirm the configuration against current official requirements, test representative payroll cases and keep evidence of approvals before relying on a production pay run.

Which Figures Should Be Reviewed Before Payroll?

Review the currently applicable salary tax rules, minimum wage notifications and contribution bases relevant to the workforce. Check the current notified figure with the responsible authority rather than using an unverified rate table. Record the source and effective date so later reviewers can understand why a setting was used.

What Should Be Checked When An Employee Leaves?

Review the applicable notice provisions, unpaid earnings, approved deductions and any entitlement to leave encashment, gratuity or provident fund benefits. These do not follow one universal formula for every worker. HR and finance should reconcile the supporting records and obtain legal review where the employee’s coverage or entitlement is disputed.

How Often Should A Compliance Register Be Updated?

Use a regular review cycle and update the register when an official notification, tax change or operational change affects the business. Opening a branch or changing employee categories can also require reassessment. Assign responsibility for checking sources, approving changes and recording when a revised policy or calculation becomes effective.

Sources

Feature details are checked against PayPeople’s product pages and help guides. Laws and settings change; confirm current rules with the official source.

Written ByPayPeople Team

The PayPeople product and implementation team writes these articles from daily work with HR and payroll teams across Pakistan. PayPeople is part of Bilytica.

Meet the Team

See PayPeople Payroll Compliance in Action

Book a walkthrough with our team using your own policies and employee data.