There are dozens of HRMS products targeting Pakistani businesses. Most of them advertise the same list: payroll, attendance, leave management, performance reviews. After working in HR operations at a Pakistani IT firm and evaluating more than a dozen platforms, I've found that the feature list is almost never the problem. What separates a system that actually gets used from one that gets abandoned 90 days after purchase is how well those features handle the specific realities of running HR in Pakistan.
Here are the five features that matter most — not as categories, but as specific capabilities.
1. Pakistani Statutory Compliance Built In (Not Bolt-On)
This is the one that fails most often in imported HR software.
Pakistan-specific compliance requirements that your HRMS must handle natively:
EOBI: Calculates at 5% employer / 1% employee on the statutory minimum wage (PKR 37,000 for Punjab in 2026), not on gross salary. Any system that calculates on actual salary is giving you wrong numbers.
PESSI / SESSI / ESSI: Province-aware contributions at 6% employer-only, capped at the insurable wage ceiling of PKR 30,000. An employee in Lahore enrolls with PESSI; an employee in Karachi with SESSI. These are different employer codes, different remittance portals, different challans.
FBR Income Tax: Tax slabs under the Income Tax Ordinance 2001, updated each Finance Act. Most imported HR systems don't ship with Pakistan FBR tax tables. You end up calculating tax in Excel and importing the result, which defeats the purpose of having an HRMS.
Gratuity: The mandatory end-of-service gratuity calculation under the West Pakistan Industrial and Commercial Employment (Standing Orders) Ordinance 1968 — one month's last drawn salary per year of service for permanent employees.
Leave encashment: Rules differ between Punjab and Sindh employment ordinances regarding which leaves can be encashed and at what rate.
A genuine Pakistani HRMS ships with all of this pre-configured and updates the tables automatically when laws change. A generic global HRMS makes you configure it yourself — which means every Finance Act update, every minimum wage revision, and every EOBI threshold change becomes a manual maintenance task for your HR team.
What to look for: Ask the vendor: "What happens when Punjab revises the minimum wage in July 2026?" The answer should be "we push an update automatically." If the answer is "you update the settings in configuration," walk away.
2. Attendance That Integrates with Biometric Devices (Not Just Manual Entry)
Pakistani companies use biometric attendance devices. The market leaders — ZKTeco, Suprema, Hikvision, Anviz — are everywhere. And yet most HRMS products ask you to manually export data from the device and import it into the system.
The problem with manual import: it's typically done once a week or once a month, which means attendance reports are always a week behind. Late-coming deductions are applied after the fact. Managers can't see who's actually present today. The system's "attendance" data is a retrospective record, not a live operational tool.
What you actually need:
Real-time biometric sync: The HRMS connects directly to the biometric device via API or local network polling. When an employee scans their card or fingerprint at 9:14 AM, the HRMS shows "late arrival" within seconds — not at the end of the month when the batch import runs.
Automatic late deduction rules: Pakistani payroll includes late-coming deductions (typically 1/30th of salary per absent day, or tiered deductions per company policy). These should calculate automatically from biometric data, not from a manual calculation the HR team runs every payday.
Leave integration: When an employee applies for leave through self-service and it's approved, that day should show as "leave" in attendance automatically — not require a separate manual update to the attendance system.
Overtime flagging: If your employee works past 6 PM, the system should flag it for manager review and payroll inclusion rather than losing the data.
A company with 50 employees and manual attendance processing spends approximately 8 hours per month reconciling biometric records, cross-referencing leave requests, calculating deductions, and correcting errors. With proper biometric integration, that drops to under an hour.
3. Self-Service Portal That Actually Works on Mobile
This one is easy to underestimate. Pakistani employees increasingly expect to handle routine HR tasks from their phones — applying for leave, checking salary slips, submitting expense claims, viewing their EOBI and tax information.
The business case is simple: every routine request that goes through HR instead of through a portal consumes HR bandwidth on zero-value-added work.
A typical mid-sized Pakistani company receives:
- 30–50 leave requests per month
- 20–40 salary slip requests
- 15–25 document requests (employment letters, experience certificates)
- 10–20 expense submissions
If each takes 5 minutes of HR time, that's 375–575 minutes per month — nearly 10 hours — on administrative requests that a self-service portal handles instantly.
What a genuine self-service portal includes:
- Leave application and approval workflow (with manager notification)
- Salary slip download (current month and 12-month history)
- Tax certificate (Form 16 equivalent, relevant for FBR filing)
- EOBI insurance number and contribution history
- Document requests (auto-generated employment letters with letterhead)
- Profile updates (address, emergency contact, bank account)
The mobile requirement: Urdu UI is a bonus but not essential — most Pakistani corporate employees are comfortable with English. What matters is that the mobile experience is functional on a PKR 25,000 Android mid-range phone with a 4G connection, not just on a MacBook in a Lahore office. Many HRMS self-service portals are designed for desktop and technically "work" on mobile but are unusable in practice.
4. Payroll That Handles Pakistan's Complexity Without Manual Adjustments
Pakistani payroll has more moving parts than a straightforward "gross salary minus tax" calculation. An HRMS that handles only the basics leaves HR doing the rest in Excel.
Pakistan-specific payroll components your HRMS should calculate natively:
| Component | What it requires |
|---|---|
| Basic salary | Base for gratuity, EOBI, and provident fund calculations |
| House rent allowance | Typically 45% of basic per Standing Orders or company policy |
| Medical allowance | Fixed or percentage; exempted from income tax up to PKR 10,000/month |
| Conveyance allowance | Tax-exempt up to PKR 2,500/month |
| EOBI deduction | 1% of statutory minimum wage, shown as separate line |
| PESSI/SESSI deduction | Employee contribution — currently nil; structure reserved |
| EOBI employer cost | 5% — expense line, not employee deduction |
| PESSI/SESSI employer cost | 6% of insurable wage — expense line |
| Income tax | Per FBR slabs, annualized, deducted monthly |
| Gratuity provision | 1/12th of last month basic per month — accrual tracking |
| Provident fund | If applicable — 8.33% or company rate, employer matching |
| Overtime | 2× hourly rate for hours beyond 48/week (Factories Act) |
| Advance deduction | Salary advance repayment tracking |
| Late deduction | Per late-coming policy |
A payroll system that requires manual entry for tax, manual adjustment for advance deductions, and a separate Excel file for gratuity tracking is not saving you time — it's just moving the problem from paper to screen.
The payroll finalization test: Ask the vendor to demonstrate running payroll for 20 employees with three on leave, two with advances, one late-joining, and one on their last working day (with gratuity). If the demonstration requires switching to a spreadsheet at any point, the system isn't ready for Pakistani payroll.
5. Reporting That Answers Real Questions Without Custom Development
Every HRMS vendor claims powerful reporting. What actually matters is whether the reports answer the questions Pakistani HR teams and CEOs actually ask:
Questions that should be answerable in under 60 seconds:
- "How much EOBI did we pay last quarter vs. this quarter, broken down by department?"
- "Which employees are due for their annual increment in the next 30 days?"
- "What's our total compliance cost per employee (EOBI + PESSI + tax employer burden)?"
- "How many employees have been absent more than 3 days this month?"
- "What is our total payroll expense by cost center for the last 6 months?"
- "Which employees haven't taken their annual leave and carry more than 15 days forward?"
If the answer to any of these requires an IT request, custom query development, or an Excel export and pivot table: the reporting isn't built for your use case.
What proper reporting looks like:
- Pre-built compliance reports: EOBI summary, PESSI/SESSI summary, income tax deduction register
- Attendance analytics: punctuality trends, department-level comparisons, leave balance aging
- Cost analytics: headcount cost by department, year-over-year payroll growth, compliance cost as % of payroll
- HR analytics: turnover rate, average tenure, offer-to-join conversion
Export should be one click to Excel or PDF — not a prerequisite to get the data at all.
The Evaluation Checklist
Before signing any HRMS contract, test these five things:
- Run a payroll calculation for one employee with EOBI, PESSI, and income tax included. Compare to your manual calculation. The numbers should match exactly.
- Change the minimum wage in a test environment and see what breaks. A properly built system recalculates all compliance contributions automatically.
- Submit a leave request from a mobile phone on 4G. If it takes more than 90 seconds to complete, your employees won't use it.
- Generate the EOBI PS-1 challan. It should come out pre-filled with your employer code, month, headcount, and total amount — ready to take to the bank.
- Pull a compliance cost report for the last three months. It should include EOBI, PESSI, and tax — no spreadsheet required.
Frequently Asked Questions
Q: Should I buy a global HRMS like SAP SuccessFactors or Workday for my 60-person Pakistani company? A: Almost certainly not. These platforms require expensive implementation partners and extensive localisation work to handle Pakistani compliance. The total cost of ownership for a 60-person company often exceeds the platform's value within 18 months.
Q: What's the difference between an HRMS and a payroll system? A: A payroll system handles salary calculation and disbursement. An HRMS includes payroll but also manages recruitment, onboarding, attendance, leave, performance, and compliance. Most Pakistani companies need the HRMS layer — payroll-only systems leave you with disconnected tools.
Q: How long does it take to implement an HRMS for a 50-person company? A: With proper vendor support and an organised data migration (employee records, salary structures, historical attendance), implementation typically takes 2–4 weeks. If a vendor quotes you 6+ months for a 50-person deployment, that's a red flag about either the product or the support model.
Q: Can an HRMS integrate with our existing accounting software (QuickBooks, Xero)? A: Many HRMS products offer accounting integrations. More important than the integration is whether it exports the right journal entries — cost center splits for payroll, separate lines for compliance provisions (EOBI, PESSI), and accurate tax liabilities. Verify this specifically during the demo.
Final Note
The best HRMS for a Pakistani company is one that removes compliance anxiety — the monthly dread of whether your EOBI numbers are right, whether your PESSI challan will clear, whether your tax deductions will survive an FBR audit. When those questions disappear from your mental load, you can spend HR time on things that actually matter to your people.
See how Workflow Engine handles all five areas in one platform — book a 30-minute live demo.
Adnan Khan
HR Lead, Bitsbuffer
Adnan leads HR operations and business development for Workflow Engine. He writes about Pakistani HR compliance, payroll, and workflow automation from direct operational experience.