HR and payroll, built for Pakistan
Attendance, leave and salary, run the way a Pakistani payroll department actually works.
PayFolk is for companies running attendance based or salaried payroll in Pakistan, any size that has outgrown a spreadsheet or a paper register. Province aware statutory compliance, a check-in built for the phones your staff carry, and a payroll run you can defend three years later, all in one place.
Sales led onboarding: a request goes to a person, not a checkout page. No price is quoted until someone has looked at what your company actually needs.
Attendance
A check-in that works on the phone your guard actually has
Consumer GPS on the phones this product targets is accurate to about 100 metres. A tight geofence does not catch anyone cheating, it just locks honest people out of marking their own attendance, so the radius is generous by default and every read the phone cannot trust is treated as unknown rather than as an ejection.
Geofenced check-in, sized for real GPS
Work sites define a radius, never smaller than 50 metres, because anything tighter sits inside ordinary phone GPS error. A reading with no real fix is treated as unusable, not as outside the fence.
The muster grid, on screen
Present, Absent, Late, on leaVe, Holiday, Weekly off: the same six letters a paper register already used. Half day is a half mark, and a day nobody recorded is a dot, never counted as absence.
Payroll
A payslip you can defend in an argument, three years later
Money is stored as whole paisa, never a float, and every payslip's lines sum to its own total exactly. Once a run is locked it is never edited again: a correction is a new run, on the record, not a quiet change to a payslip someone already has on paper.
Paisa-integer money
No rounding drift, ever. A rupee of difference between a payslip's lines and its total is the fastest way to lose a team's trust, so the arithmetic never allows it.
Immutable, once locked
A finalised run cannot be edited. Every run keeps a snapshot of its own inputs, so the same payslip regenerates identically whenever it is looked at again.
Province-aware statutory rules
EOBI, and PESSI or SESSI depending on the branch's province, are versioned platform config, not something a company edits. Tax withholding runs against the July to June fiscal year, projected properly rather than guessed at ×12.
How it is built
Your rules are configuration, not a project
Rounding, the leave year, how many lates cost a day, who gets a bonus and when: every company sets these on its own settings page. Nothing about your policy ever becomes an if-statement written just for you, which is what keeps onboarding a form to fill in rather than a months-long integration.
Config, not code
Your rounding rule, your leave year start, your lateness threshold, your bonus conditions: all settings, never a custom build. The same engine runs every company, which is why a change ships to everyone at once and nothing is a one-off.
Isolated by construction
Every company's records are kept apart at the data layer, proven by an automated isolation suite that fails the build if a query is ever missing its scope. Your payroll data never shares a query with anyone else's.
Modules
Turn on what your company needs
Employee records are the one thing every company has on from day one. Everything else, attendance, leave, payroll, loans, self service and the rest, is switched on per company, so a business that only needs attendance is not paying for a recruitment pipeline it will never open.
Employee recordscore
The employee master, documents and job history.
Attendance & time
Shifts, rosters, check-in and overtime.
Leave
Leave types, accrual, balances and approvals.
Payroll
Salary structures, payroll runs, payslips and bank files.
Loans & advances
Requests, schedules and payroll recovery.
Separation
Resignation, clearance and final settlement.
Letters & documents
Policy documents published for employees, plus generated HR letters.
Reports
Headcount, attendance, payroll register and statutory returns.
7 modules beyond employee records, each one a switch your account manager sets for you, not code written just for your company.
Ready to leave the spreadsheet behind?
Tell us about your company and we will get in touch. No account is created until we have talked, and no price is published anywhere.
Questions
Before you write in
- Why can't I just sign up?
- Because pricing is negotiated per company, not published on a page, and setting up a company's account is a decision a person makes, not something a public form should be able to trigger on its own. Filing a request costs you two minutes and gets you a real answer instead of a plan picker.
- Do my employees need a personal email address?
- No. Everyone signs in with an email and a password, but an employee without one is given a company address by their HR admin. There is no phone or employee code sign-in door to remember, just the one you were given.
- How is my company's data kept apart from everyone else's?
- Physically separated at the database layer, and checked by an automated isolation suite on every change to the codebase, not just a filter in application code that someone could forget.
- How long does onboarding actually take?
- Your policies are configuration, so setup is filling in settings, not commissioning custom code. Most of the time is your data: employees, salary structures and opening leave balances, not waiting on a build.