An HR Information System (HRIS) is software that stores and manages all of a company’s employee data in one place — records, attendance, leave, payroll, hiring and performance. For Pakistani businesses, a useful HRIS also handles EOBI contributions, provincial social security (PESSI in Punjab, SESSI in Sindh), and FBR salary-tax slabs without manual workarounds. Cloud HRIS pricing in Pakistan starts around Rs. 400 per employee per month.
An HR Information System is a central database for everything your company knows about its employees, wrapped in the workflows that keep that database current.
That second half is the part people miss. Plenty of companies already have a “central database” — it’s a folder on the HR manager’s laptop with forty spreadsheets in it. The reason that folder is always out of date is that nothing forces it to update. Someone gets promoted, the promotion letter gets signed, and the salary sheet gets corrected two payroll cycles later when the employee complains.
An HRIS closes that gap. The promotion is entered once, and the org chart, the payroll calculation, the leave entitlement and the reporting line all change from that single entry.
In a Pakistani context, an HRIS usually covers:
Vendors treat these as three product tiers. In the Pakistani market they’re used interchangeably, and you’ll see the same software sold under all three names.
The textbook distinction:
| Term | What it emphasises | Typical scope |
| HRIS | Information and records | Employee data, documents, org structure, basic reporting |
| HRMS | Operations and processes | Everything in HRIS, plus payroll, attendance, recruitment, performance |
| HCM | Strategy and workforce planning | Everything in HRMS, plus succession planning, workforce forecasting, learning management |
Our advice: ignore the label on the box and ask for the module list. A platform calling itself an HRIS that runs payroll and attendance is more useful to you than an “HCM” that doesn’t handle EOBI. We’ve covered the module-level breakdown in more depth in our full HRMS guide for Pakistan.
Most companies here don’t switch to an HRIS because they read about digital transformation. They switch because something went wrong.
The four things that usually trigger it:
A payroll error that reached the employees. One wrong formula in a merged cell, and 60 people get paid the wrong amount on the 1st. It’s recoverable, but it costs the HR team a week and costs management some trust.
An FBR or EOBI notice. Manual records don’t survive an audit well. If your evidence of contributions is a bank statement and a spreadsheet, you’ll spend days reconstructing what should have taken minutes.
Headcount crossing roughly 40–50. Below that, one organised person with Excel can genuinely keep up. Above it, they can’t — not because they’re not capable, but because the number of exceptions grows faster than the headcount does. Ten people means ten leave balances. Fifty means fifty leave balances, plus mid-month joiners, plus unpaid leave, plus three people on probation with different entitlements.
Multi-city or multi-shift operations. A factory in Faisalabad with three shifts and a head office in Lahore cannot run attendance on paper registers that get couriered weekly.
If you’re still weighing this up, the SME-specific HRMS guide works through the numbers at a smaller scale.
This is the foundation, and it’s the module people underestimate. Every other module reads from it.
A proper master record holds personal details, CNIC and its expiry, contract type and end date, designation, department, reporting manager, salary structure, bank details, EOBI registration number, and scanned documents — CNIC copy, contract, educational certificates, medical records where relevant.
The practical benefit shows up during audits and exits. When an ex-employee disputes a final settlement, the answer is in one screen with a timestamp on every change, rather than in three people’s email.
Attendance feeds payroll, so errors here become salary errors.
Pakistani businesses typically run one of three setups: biometric devices at entry points (still the most common for factories and offices with fixed locations), mobile check-in with GPS (for field staff, sales teams, delivery), or manual marking by a supervisor (small offices, remote-first teams).
Leave is where the local complexity sits. Pakistani leave policy usually splits into casual, sick, annual/earned, and then whatever the company adds — hajj leave, marriage leave, bereavement, maternity and paternity. Entitlements often differ by grade and by length of service. The system needs to handle accrual, carry-forward rules, encashment, and the approval chain, or HR ends up recalculating balances by hand anyway.
The module most companies buy the software for.
At minimum it should produce: gross-to-net calculation for every employee, income tax deduction against current FBR slabs, EOBI employer and employee contributions, provincial social security, provident fund, loan and advance deductions, overtime, arrears, bonus handling, a bank-transfer file in your bank’s format, and individual payslips.
For the deeper mechanics — parallel runs, arrears handling, bank file formats — see the payroll software guide for Pakistan.
An applicant tracking system holds job postings, applications, interview stages, evaluation notes and offer letters.
The part worth paying for is what happens after the offer is accepted. Good onboarding automation opens the employee record, sends the document checklist, assigns the email account and system access, notifies IT and admin, and schedules the probation review — all triggered by one status change. Done manually, that’s a six-email process that gets half-completed.
AI-assisted CV screening has become standard rather than premium. We looked at how that works in practice in our piece on AI in applicant tracking systems.
Goal setting, review cycles, manager and self-assessments, ratings, and a record that persists year to year.
Honest assessment: this is the module with the lowest adoption rate in Pakistani companies. The software works. The problem is that annual reviews often aren’t a real process yet — they’re a form filled in the week before increment decisions that were already made. If that describes your company, buy the module but don’t expect the software to fix the process.
Staff log in and see their own payslips, leave balance, attendance record and documents. They apply for leave, submit expense claims and update their contact details themselves.
This is the single biggest reducer of HR workload, and it’s the module employees notice. In most companies, a meaningful share of HR’s day goes to answering “how much leave do I have left” and “can you resend my payslip.” Self-service removes that entirely.
Headcount by department, turnover rate, average tenure, cost per head, attendance trends, overtime concentration, gender split, salary band distribution.
The reports that actually get used by management in Pakistani companies tend to be narrower than the dashboards vendors demo: monthly salary cost against budget, overtime by department, and attrition in the first 90 days. Start there.
This is the section that decides whether an international platform will work for you. It usually won’t.
EOBI. Registration is mandatory for establishments with five or more employees under the EOBI Act 1976, and registration is required within 30 days of crossing that threshold. Contributions are calculated against an EOBI wage ceiling that is revised periodically — not against the employee’s full salary. Applying a flat percentage to gross salary is the most common EOBI error we see in spreadsheets, and it produces both underpayment and audit exposure. Check the current ceiling at eobi.org.pk before your first run.
Provincial social security. PESSI in Punjab, SESSI in Sindh, with equivalents in KP and Balochistan. Rules, wage thresholds and contribution rates differ by province. A company with offices in Lahore and Karachi is dealing with two separate systems, and the software has to know which employee falls under which.
FBR salary tax. Slabs are revised through the annual Finance Act. This is the single most common reason spreadsheet payroll breaks — the formulas were correct last year and are silently wrong from July. An HRIS with pre-configured slabs updates centrally; you don’t have to remember. Withholding under Section 149 must be deducted and deposited on schedule, with statements filed.
Minimum wage. Set provincially and revised in provincial budgets. Relevant for factories and any operation with a large entry-grade workforce.
Gratuity and provident fund. Calculation depends on tenure and last drawn salary. Getting this wrong at exit is how companies end up in labour court.
Labour law recordkeeping. Written contracts, attendance registers, wage records and leave records all need to be maintained and producible on inspection.
Our HR compliance guide for Pakistan covers each of these frameworks in full, with an audit checklist you can run before closing payroll each month.
Cloud HRIS in Pakistan is priced per employee per month. Expect a range of roughly Rs. 400 to Rs. 1,200, depending on modules and headcount.
| Company size | Typical modules needed | Indicative range (per employee/month) |
| Under 25 employees | Records, attendance, leave, payroll | Rs. 400 – 600 |
| 25 – 100 employees | Above, plus recruitment, ESS, basic reporting | Rs. 400 – 800 |
| 100 – 500 employees | Above, plus performance, analytics, multi-branch | Rs. 500 – 1,000 |
| 500+ / multi-province | Full suite, custom integrations, dedicated support | Custom quote |
PayPeople starts at Rs. 400 per employee per month, billed in PKR.
Costs vendors don’t always put on the quote:
On USD pricing: international platforms quote in dollars. At Pakistani headcounts this is usually the deciding factor — a platform at $6 per employee per month costs several times a local equivalent, and your cost moves with the exchange rate every renewal. PKR billing removes that variable entirely.
A note on how to compare quotes. Ask every vendor for the same thing: total annual cost for your exact headcount, all modules you need, implementation included, for two years. Per-employee headline pricing hides too much.
Run through this before you sit through a single demo.
1. Write down your three real problems first. Not “we need to digitise HR.” Something like: payroll takes five days, we can’t produce attendance records for the last quarter, and nobody knows the actual headcount. Every demo should then be judged against those three things.
2. Confirm local compliance is native, not custom. Ask directly: is EOBI pre-configured, or do we set up a custom deduction? Are FBR slabs updated by you when the Finance Act changes, or by us? Is PESSI and SESSI handled separately? The answers separate genuinely local software from international software with a Pakistani reseller.
3. Check where the data lives. For many Pakistani companies — especially those working with government, banks or telecoms — local data residency isn’t a preference, it’s a procurement requirement.
4. Test support in your working hours. Send a support query at 11am on a Tuesday during evaluation and see what happens. A vendor with a support team in a different timezone will answer your urgent payroll question at 3am your time.
5. Ask about your existing biometric hardware. If you already own devices, replacing them adds real cost. Confirm integration before you commit.
6. Insist on a parallel payroll month. Run your existing process and the new system side by side for one cycle before cutover. Any vendor who resists this is telling you something.
7. Look at what happens when you leave. Can you export your complete employee data, payroll history and documents in a usable format? Get the answer in writing.
| Local Pakistani HRIS | International platform | |
| EOBI / PESSI / SESSI | Built in | Custom configuration or manual |
| FBR slab updates | Handled by vendor | Your responsibility |
| Billing currency | PKR | Usually USD |
| Support hours | Pakistan business hours | Varies, often offshore |
| Global multi-country payroll | Limited | Strong |
| Integrations with global tools | Fewer | Extensive |
If your entire workforce is in Pakistan, local wins on the things that break payroll. If you have entities in multiple countries, the calculation changes. We compared one specific case in PayPeople vs WebHR.
A typical SME rollout takes 2–4 weeks. Multi-branch enterprise rollouts run 6–8 weeks. Here’s the sequence that works.
Step 1 — Decide what goes live first. Do not switch on every module at once. Records, attendance and payroll in month one. Recruitment, performance and analytics in month two or three. Companies that try to launch everything simultaneously end up using none of it properly.
Step 2 — Clean your employee data before you import it. This is the step that determines whether the project runs on time. Verify CNIC numbers, joining dates, current salary, designation and reporting manager for every employee. Expect to find errors — in most companies, somewhere between 5% and 15% of records have at least one wrong field. Fix them in the spreadsheet, not after import.
Step 3 — Import your org structure. Departments, designations, reporting lines, cost centres, locations. This becomes your digital org chart and drives every approval route in the system.
Step 4 — Configure roles and permissions. Decide who sees salary data. Decide whether managers see their team’s records only or the whole company. Get this wrong and you’ll have a confidentiality incident in week one.
Step 5 — Set up compliance parameters. EOBI wage ceiling, provincial social security by location, current FBR slabs, provident fund rules, gratuity policy, leave entitlements by grade. Have your finance lead sign off on these before the first run.
Step 6 — Run one parallel payroll month. Process the same month in both the old and new system. Compare every line. Investigate every difference — some will be old errors the new system caught, which is exactly what you want to find now rather than later.
Step 7 — Onboard employees to self-service. Send logins, ask staff to verify their own personal details and upload missing documents. Employees find errors in their own records that HR never would.
Step 8 — Train managers, not just HR. Department heads approve leave and review team reports. If they don’t use the system, approvals go back to WhatsApp and the record stays incomplete. Two short sessions is usually enough.
Step 9 — Cut over and archive the old process. Set a hard date. Keep the spreadsheets read-only for reference, but stop updating them. Running both systems “for a while” is how companies end up with two sets of records and neither one correct.
Importing dirty data. Covered above, but worth repeating — it’s the single biggest cause of failed rollouts. The system inherits every error in your spreadsheet and then makes it authoritative.
Buying modules nobody owns. Every module needs a person responsible for it. If nobody owns performance management, buying the performance module changes nothing.
Skipping the parallel run. Cutting straight over means your first live payroll is also your first test. If it’s wrong, everyone finds out on payday.
Leaving compliance settings on defaults. Default tax and contribution settings are placeholders. Someone has to check them against current rules and sign off.
Treating go-live as the finish. Adoption happens over the following two months, not on launch day. Somebody needs to keep checking that managers are actually approving in the system.
This is worth taking on its own, because accuracy is what everything else depends on. A payroll module is only as good as the salary figures underneath it.
One record, not several. In a manual setup the same employee exists in a leave register, a salary sheet, a recruitment file and an attendance log. Four copies, four chances to be out of date. An HRIS keeps one record and shows it in four places.
Validation at entry. The system rejects a malformed CNIC, a joining date in the future, or a salary field left blank. Errors get caught by the person entering them, not by the employee reading their payslip.
Employees maintain their own details. Staff update their own phone number, address and emergency contact through self-service. HR was never going to chase 200 people for a new address. Employees will update it themselves when they can do it from their phone.
Changes propagate automatically. A promotion entered once updates the org chart, the payroll calculation, the leave entitlement and the approval routing. In a spreadsheet system, that’s four separate edits, and the fourth one gets forgotten.
Every change is logged. Who changed what, when, and what the previous value was. During an audit or a settlement dispute, that log is the answer.
Modules read from the same source. Attendance flows into payroll without re-entry. Nobody retypes 200 rows from one sheet into another, so nobody makes typos doing it.
Under 20 employees. Usually not yet, unless you’re multi-location or have complicated shift patterns. One organised person can manage this in spreadsheets. Spend the money elsewhere.
20–50 employees. The crossover point. If payroll takes more than a day, or you’ve had a salary error in the last six months, you’re past it.
50–200 employees. Yes. At this size, manual HR is consuming a full-time role’s worth of effort in avoidable work, and the compliance exposure is real.
200+ employees. Not a question of whether, only which one and how well configured.
By industry: factories and manufacturing need attendance and overtime accuracy above everything — see the HR solution guide for manufacturing companies. Software houses and agencies care more about leave, performance and remote check-in. Retail chains need multi-location attendance and high-turnover onboarding. Hospitals and schools need shift rosters and credential tracking.
