Every payroll demo looks good. The screens are clean, the sample payslip is right, and the sales team answers every question with a yes. The real test comes months later: a disputed payslip, a rate change, a staff member who leaves, or a vendor that stops answering.
This checklist helps you compare payroll systems on what matters after you sign. It does not tell you what the law requires. For that, talk to a payroll specialist or an accountant who knows your industry.
Start with your own process
Before you look at any product, write down how payroll works today:
- How many staff, legal employers and sites you pay.
- How you pay them: monthly, daily or by the hour, and how often.
- Where the hours come from: a biometric device, a DTR in Excel, or a time clock app.
- Who prepares payroll, who checks it, and who releases the money.
- Which reports you send to your accountant, and in what format.
This list becomes your test script. If a vendor cannot show your process, with your kind of staff, the product may not fit.
The buyer checklist
1. Where does the time data come from?
Most payroll errors start in the timesheet, not in the payroll calculation. Ask how hours, late minutes, overtime and leave reach payroll. Is it typed in, imported from a file, or carried over from approved timesheets? The fewer times a number is copied by hand, the fewer errors you get. Ask how the system handles a shift that crosses midnight.
2. Who approves what?
Look for approvals at each stage: the supervisor approves the time, a payroll officer prepares the run, and a different person approves it before release. Ask whether the system stops one person from preparing and approving the same run. A good system enforces this. A weak one only suggests it.
3. Is there an audit trail?
Ask to see the history of one payslip. You should be able to answer:
- Which approved hours and leave fed into it.
- Who changed a rate, an adjustment or a deduction, and when.
- What the payslip looked like before a correction.
If the vendor cannot show you this in the demo, assume it is not there.
4. Who keeps the rates and rules up to date?
Contribution tables, tax tables, minimum wages and holiday lists change. Ask the vendor who updates them, how fast, and how you will know. Ask whether each rate shows its source and the date it takes effect. Ask what happens to a payroll period that spans a change. Be wary of any vendor that cannot say who checks the rules before they go live.
5. Can you get your data out?
Buyers often forget to ask this. Ask for an export of employees, pay history, payslips and the audit log, in a format you can open without the vendor, such as CSV. Ask whether you can run it yourself at any time, or whether you must request it. Then test it during the trial. Your records belong to you, and you may need them for years.
6. Is the vendor stable?
A payroll vendor holds your most sensitive records and sits between you and your staff's pay. If it stops operating, you need a plan. This is a real risk, not a theory. In January 2024, DealStreetAsia reported that Philippine payroll provider Salarium had suspended operations. The lesson for buyers is not about one company. It is about your own exit plan.
- Keep a regular export of your payroll data outside the system.
- Know how you would run one payroll by hand if you had to.
- Ask how long the vendor has operated, and who supports the product.
- Read the contract terms on data return when the service ends.
7. How is access controlled?
Payroll shows every salary in the company. Ask whether each user can have a role limited to their own branch or legal employer. Ask whether multi-factor authentication (a code from a phone as well as a password) is available, and whether you can make it compulsory. Ask how the vendor protects the data and who on their side can see it.
8. What do employees see?
Staff ask about their pay, leave and hours. A system where they can see their own payslips and leave balances on a phone saves HR many questions. Check that each person sees only their own records.
9. Reports for government and the bank
Ask exactly what the system produces for SSS, PhilHealth, Pag-IBIG and BIR. Is it a summary you check and file yourself, or does it file for you? Ask for a sample and show it to your accountant. For bank payroll files, ask whether the format was tested with your own bank. Do not accept a general "yes".
10. Can you run it in parallel first?
Never switch payroll on trust. Run the new system next to your current payroll for at least one period, ideally two. Compare each person's gross pay, deductions and net pay. Look into every difference until you understand it. Only then move real pay to the new system. The payroll parallel run checklist shows how.
If you pay piece-rate or pakyaw workers
Some workers are paid by output, not by the hour or the day. Piece-rate pay counts the pieces each person makes. Pakyaw usually means a set price for a whole job, often shared by a team. Many payroll systems handle neither well, so ask about them early, with your own examples.
- How do you record output for each person or team, for each day, and who approves it?
- Can one person have time-based pay and output-based pay in the same period?
- Where do the rates per piece or per job live? Does each change keep a date and a name in the audit trail?
- How is one pakyaw job split between the members of a team, and can you see the split on each payslip?
- How does the system handle the statutory parts of pay for workers paid by output, and who checked that logic?
- Can you include your piece-rate and pakyaw workers in the parallel run?
Show the answers to a payroll specialist before you decide. Workforce Pinas does not compute piece-rate or pakyaw pay today.
A quick scorecard
| Question | A good answer |
|---|---|
| Where do hours come from? | Approved timesheets, with no retyping |
| Can one person prepare and approve a run? | No, the system refuses it |
| Can I see who changed a payslip? | Yes, with the time and the old value |
| Who updates the rates? | A named team, with a source and a date for each rate |
| Can I export all my data? | Yes, in CSV, whenever I want |
| What if you stop operating? | A clear data return process in the contract |
| Can we run it in parallel? | Yes, and the vendor helps compare the results |
Red flags
- A vendor that will not show the product with your own sample data.
- Claims of full compliance with no detail on who checks the rules.
- No self-service data export.
- Pressure to switch payroll without a parallel run.
- No clear answer on who to call when payroll is due tomorrow.
Where Workforce Pinas stands
We build Workforce Pinas to answer these questions plainly, so here are our own answers. Approved timesheets and leave carry into a payroll run. By default, a person who prepared a run cannot approve it. Changes go to an audit log, and reports export to CSV. Contribution and withholding summaries are exports for you to check, not a filing. A go-live page lets you record parallel runs against your current payroll before you use it for real pay.
Payroll is in pilot review. Statutory rules and payroll results require specialist validation before production use. Read more on the payroll page, see how DTR and timesheets feed it, or ask us for a demo.
If your hours still come from a spreadsheet, start with DTR template or time clock app.
