Zaffre AxonDemo
← All articles

How to Set Up Multi-Location HR in Pakistan: A Practical Playbook

Zaffre HRM Team · May 30, 2026

A business operating in Karachi, Lahore and Islamabad needs a different HR setup from a single-location business in Lahore. Province-specific social security, provincial minimum wage, per-location attendance, consolidated payroll, and aggregated reporting all need to be planned from the start. Adding multi-location HR a year after launch is painful. Here is how to set it up.

The 8-step multi-location HR setup

1. Decide your legal entity structure

Are all locations under one legal entity? Or one entity per province? This affects taxation, registrations, and reporting. Most Pakistani SMBs operate as a single entity with multiple "establishments." Confirm with your tax advisor.

2. Register at each location

Each operating location may require:

  • Provincial Shops & Establishments registration
  • Provincial social security (PESSI in Punjab, SESSI in Sindh, KPESSI in KP, BESSI in Balochistan). See the PESSI guide
  • Provincial professional tax registration. See professional tax
  • EOBI is federal, so a single registration covers all locations

3. Build location-aware employee records

Each employee has a primary location. The system must know it. Compliance contributions, the applicable minimum wage and reporting jurisdiction all follow from it.

4. Set per-location attendance policy

An office in Karachi may keep different hours from a warehouse in Faisalabad. Shift patterns may differ. Public holidays can differ slightly too, since some are province-specific. You need settings per location.

5. Consolidated payroll, location-aware

One payroll cycle covers all employees, but each employee gets the correct provincial SS, minimum wage and overtime tier rules. You get per-location cost reports plus a consolidated company report.

6. Per-location managers and RBAC

A location manager can see their own location's data and nothing else. Head office HR sees everything. Role-based access has to be scoped by location.

7. Multi-location asset tracking

Assets allocated per location. When an employee transfers from Karachi to Lahore, their assets either move with them or return to Karachi inventory. Asset register tracks this.

8. Aggregated reporting

Headcount per location, payroll cost per location, attendance trends per location, leave patterns per location. Plus year-on-year, month-on-month and location-vs-location comparisons.

The cross-province compliance map

Province-specific items

  • Provincial social security (PESSI / SESSI / KPESSI / BESSI): different rates
  • Provincial minimum wage: different amounts
  • Provincial Shops & Establishments registration: each one separately
  • Professional tax: each one separately
  • Some labour law differences (how notice periods are read, leave entitlements)

Federal items (same everywhere)

  • EOBI
  • FBR income tax (WHT under section 149)
  • Industrial & Commercial Employment Ordinance basics
  • Maternity & Paternity Leave Act (with provincial variations)

The reporting structure that works

Bottom-up view

Location → department → team → individual. A manager sees their team, a location head sees their location, and head office sees the whole company.

Compliance view

By statutory category (EOBI, PESSI, SESSI, etc.) for filing returns. By province for provincial-specific reports. Federal-level consolidated for FBR.

Cost view

Per-location cost (payroll plus operations). Per-employee fully-loaded cost (salary, benefits, statutory and facility). Per-department cost.

What multi-location HR software must support

  • Per-employee location field
  • Per-location attendance / leave / overtime / payroll policy
  • Location-aware provincial compliance
  • Per-location asset tracking
  • Per-location and consolidated reporting
  • Location-scoped RBAC for managers
  • Multi-location transfer workflow

The common mistakes

  • One-size-fits-all attendance / shift policy across locations
  • Single provincial SS used for all locations (should be per-location)
  • One minimum wage hard-coded, which breaks when provinces revise at different times
  • No location field on the employee record, so location-specific reports are impossible
  • Manager RBAC not scoped by location, so the Karachi manager sees Lahore data

The Zaffre HRM fit

Zaffre HRM supports multi-location setup with per-location attendance / leave / payroll policy, location-aware provincial compliance, per-location reporting, location-scoped RBAC and multi-location transfer workflows, all in one system. See city-specific guides: Karachi, Lahore, Islamabad.

Book a demo for multi-location configurations.