TL;DR: An HR software evaluation checklist turns a vendor shortlist into a decision. Work through it in five stages: your own requirements, payroll integration, Australian compliance, data migration and implementation, then demos and reference calls. Score every vendor against the same questions, ask for answers in writing, and treat anything a vendor offers to build later as not yet available.

Key takeaways

• Most HR software checklists stop at features, yet the questions that decide whether a system lands are about payroll sync, migration and implementation effort.
• Ask which fields move between the HRIS and payroll, in which direction, and on what trigger, because “two-way” describes direction rather than coverage.
• According to the Workplace Gender Equality Agency, employers with 100 or more employees must report every year. Its 2025 survey found reports took 41 hours on average to prepare.
• According to the Fair Work Ombudsman, time and wages records must be kept for seven years and cannot be false or misleading.
• Reference customers of your size and shape are the best evidence you can get, so prepare specific questions rather than asking whether they are happy.

What is an HR software evaluation checklist?

An HR software evaluation checklist is a structured list of questions you put to every vendor on your shortlist, in the same order. That way you compare answers rather than impressions. It covers requirements, payroll integration, compliance, security, data migration, implementation effort, demos and references. The answers then feed a scoring matrix that records each vendor’s evidence.

Checklist, requirements list, matrix or RFP?

The four terms overlap, and buyers use them loosely. A requirements checklist lists what your organisation needs, written before you speak to anyone. An evaluation checklist adds the questions that test whether a vendor genuinely meets each need. The evaluation matrix then scores those answers, usually with weights. Finally, an RFP (request for proposal) packages the whole lot into a formal document that vendors respond to in writing.

For most People and Culture teams at 50 to 1,000 employees, a written checklist and a simple matrix do the job. A full RFP makes sense when procurement rules require one, when the purchase crosses a spending threshold, or when a board wants a documented process. In either case, the questions stay the same.

Why vendor checklists fall short

Most checklists on page one of search results are published by HR software vendors, so they list the features those vendors sell. They rarely ask about payroll sync direction, who does the data migration, or how many hours your own team will spend on setup. Those questions decide whether a system lands, and they are the ones a sales demo tends to skip.

Suppose three vendors all tick “leave management”. One sends approved leave to payroll automatically, one holds it for a payroll admin to submit, and one needs someone to key it in again. The tick is identical; the Monday morning is not. If you are earlier in the process, the companion guide on how to choose HR software covers building the shortlist in the first place.

What should you settle before you contact any vendor?

Settle your own requirements first. That means the five or so things you cannot live without, the structural quirks of your workforce, and the source of truth for each type of data. Also agree who else has to sign off. Without that, every demo sets the agenda for you, and the systems start to blur together.

Stage one: your own requirements

• Have you written down your five must-haves, in priority order, before seeing any demo?
• Which workforce quirks would break a generic system, such as concurrent positions, multiple entities or several awards?
• For personal details, pay rates, leave balances and documents, which system is the source of truth?
• Which tools are you keeping, such as payroll, rostering, recruitment or learning, and which are you replacing?
• Who in finance, IT or payroll needs to approve the purchase, and what does each of them need to see?
• Are you solving for the next two years or the next ten, and does everyone agree on that?

That last question matters more than it looks. Some buyers need an interim fix while a larger programme settles; others want a platform they will not revisit for a decade. Neither answer is wrong, but a shortlist built for one will frustrate the other.

Structural complexity deserves its own line. If a third of your workforce holds split contracts across entities, say so to every vendor in the first meeting. Buyers who have watched a project fail on exactly that shape tend to screen for it before features, and they are right to. It is also worth deciding early whether you want a focused HRIS or a bundle, which the piece on specialised HR software versus all-in-one sets out.

How do you check a vendor’s payroll integration properly?

Name your payroll system first. Then ask which fields move, in which direction, how often, and what someone still keys in by hand. A connector the vendor built and maintains, a third-party automation tool and an open API are three different promises. Ask which one you are actually getting.

Stage two: payroll integration questions

• Is the connection to our payroll a direct integration, a third-party connector, or an API we build against?
• Which fields travel from the HRIS to payroll, and which travel back?
• Does a new starter’s tax declaration reach payroll, or does someone re-enter it?
• When an employee changes their bank account, where is it changed and who approves it?
• How do approved leave requests reach payroll, and are balances shown to staff from payroll or recalculated?
• What happens when someone updates their details the day before a pay run?
• If the sync fails, who is told, and how quickly?

Ask for the answers in writing, per field. The most common scar tissue buyers describe is two systems holding the same person with no way to tell which copy is right. That usually traces back to a sync that covered less than the sales conversation implied. As a result, the right follow-up to “it’s two-way” is always “which fields?”

Why payroll stays in its lane

An HRIS and a payroll system are separate products, even when one vendor sells both. The HRIS holds the employee record, documents, workflows and self-service; payroll calculates and pays. Some vendors, Worknice among them, leave your existing payroll in place and integrate with it. The question then becomes how cleanly data moves, not whether you migrate payroll. The explainer on HRIS versus payroll software goes deeper on where the boundary sits.

Payday Super raises the stakes. According to the Australian Taxation Office, from 1 July 2026 super guarantee contributions must reach employees’ funds within seven business days after payday. So an error in an employee record now surfaces every pay cycle, not once a quarter.

Which Australian compliance questions belong on the checklist?

Ask how each vendor keeps the records Fair Work requires and where award and classification details live. If you have 100 or more employees, check that it can produce your gender equality report. Also ask how it evidences policy acknowledgements and work rights checks. Generic checklists written for other markets usually miss all four.

Stage three: Fair Work and award context

According to the Fair Work Ombudsman, employers have to keep time and wages records for seven years. Those records must be legible, readily accessible to an inspector, and not false or misleading. Changes are allowed only to correct an error.

• Does the system keep a history of every change to an employee record, including who made it and when?
• Can you export a complete employee file quickly if a Fair Work Inspector asks for it?
• Where is each employee’s award, classification and employment type stored, and does payroll read it from there?
• Which system interprets the award for pay, and who updates classifications after a promotion?
• Can you show that each employee acknowledged a policy, not just that you sent it?

Most HRIS products record award context while payroll or a dedicated tool interprets it. That split is normal. Therefore the question is not which product “does awards” but whether both systems agree on the classification.

Stage three, continued: WGEA and work rights

According to the Workplace Gender Equality Agency, private sector employers with 100 or more employees must lodge gender equality data each year between 1 April and 31 May. Employers that directly employ 500 or more people carry extra obligations, including selecting and meeting, or showing improvement against, gender equality targets. WGEA’s own 2025 survey drew on 1,325 responses. On average, reports took 41 hours to prepare and lodge, spread over two to four weeks.

• Can the system produce a WGEA report against the current template, and can you adjust it before lodging?
• Who keeps the report current when WGEA changes the template?
• Does the system capture visa and work rights documents, and does it check or verify them?
• Does it remind you before licences, certificates and visas expire?

If you are new to the reporting cycle, the overview of WGEA reporting in Australia covers what goes into a submission.

What should you ask about security and data handling?

Ask where your data is stored and whether any certification a vendor mentions is current and independently audited. Then ask how AI features handle personal information, and who can see what inside the system. Increasingly, your IT or cyber team holds a veto over the purchase, so get their questions onto the checklist early rather than at contract stage.

Stage four: security questions

According to the Office of the Australian Information Commissioner, it received 1,205 data breach notifications in 2025. That was an 8% rise on 2024 and the highest since the scheme began in 2018. Health service providers accounted for 19% of them. HR systems hold tax file numbers, bank details and identity documents, so this is not a box to tick quickly.

• In which country is our data stored and processed, including backups?
• Is the vendor certified against a named security standard, and will they show the certificate?
• Do AI features send personal information to a model provider, and is our data used for training?
• Can permissions restrict sensitive fields, such as salary or medical notes, to named roles?
• Is single sign-on available, and on which plan?
• Will the vendor complete our security questionnaire or data protection assessment?

Listen carefully to the answer on certification. “We follow the standard” and “we are certified” are different claims, and your auditor will ask for the certificate. A vendor that answers precisely here, including telling you what it does not have, is showing you how it will answer everything else.

How do you test data migration and implementation effort?

Ask who extracts, cleans and loads your data, and what history comes across. Then ask how long implementation takes at your size and how many hours your team will spend. Finally, agree what must work at go-live and what can follow. A timeline without named owners is a hope, not a plan.

Stage five: migration and implementation questions

• Does the vendor extract data from our current systems, or do we supply clean spreadsheets?
• Which history comes across, such as past leave, documents, performance notes and employment changes?
• Who builds our contract templates, onboarding forms and workflows?
• How long does implementation typically take for an organisation of our size and shape?
• How many hours per week will our HR and payroll people need to commit?
• Is there a named implementation manager, and do they stay with us after go-live?
• What must work on day one, and what is scheduled for a second phase?

Separate “live” from “implemented”. A system can be live for leave requests in week three while onboarding workflows arrive in month two. That is healthy, provided everyone knows the order in advance.

The offer to build it later

Be careful with any requirement a vendor answers with “we can build that for you”. Sometimes it is a genuine, routine capability. Even so, it means you are paying for software that does not yet do the job. A buyer with a failed implementation behind them has good reason to hear it as a warning. Score it as not available until it ships. The page on HRIS implementation shows what a done-for-you setup typically covers.

Your fear here is reasonable. Many buyers delay a decision because they picture months of setup and a system that ends up harder than the spreadsheet it replaced. The bar is not “better than nothing”; it is better than your current workaround, and the checklist should test that directly.

How do you run demos and score the shortlist?

Send every vendor the same three to five scenarios from your own week. Ask them to show those rather than their standard deck, and score each answer on the same scale. Weight the criteria before the first demo, so the scoring reflects your priorities rather than whichever presenter was most memorable.

A simple evaluation matrix

Keep the matrix plain. List each criterion in a row and give it a weight from one to three. Then score each vendor from zero to three, with a one-line note on the evidence. Treat your five must-haves as gates: a vendor that fails one is out, however well it scores elsewhere.

• Did the vendor show your scenario, or describe it?
• Could a manager approve leave, and an employee update details, on a phone in under a minute?
• Did the vendor say plainly where it is not the right fit?
• Were integration, security and pricing answers confirmed in writing afterwards?
• Does the total cost include implementation, add-ons and your own team’s time, not just the subscription?

Cost deserves its own row, because subscription tiers rarely tell the whole story. The companion guide on what an HRIS costs in Australia breaks down implementation, change and internal time.

A scripted demo also fixes the most common complaint from buyers mid-evaluation: after the third demo, the systems blur together. When every vendor shows the same scenarios, the differences become visible, and you can explain your recommendation to finance without relying on memory.

What should you ask reference customers?

Ask reference customers of a similar size, industry and payroll system what implementation actually involved. Then ask what they stopped using, which fields still get keyed in twice, and how support responded when something broke. Specific questions produce specific answers; asking whether they are happy produces a polite yes.

Questions for reference calls

• How long did implementation take from signing to go-live, and what slipped?
• Which payroll system do you use, and what do you still enter by hand?
• Which module or feature did you buy and then stop using, and why?
• How much of your own team’s time did setup take, week to week?
• When something broke, how quickly did support respond, and did they fix it?
• Did your employees adopt it, including staff who are not at a desk?
• What would you check more carefully if you were choosing again?

The question about what they stopped using is the most revealing one. Buyers rarely abandon a system because it breaks; they drift back to a workaround that feels easier, often without anyone deciding to. Ask for at least one reference that went live in the last year, since the implementation process may have changed since older customers joined.

How should you make the final decision with an HR software evaluation checklist?

Rule out any vendor that fails a must-have, compare the rest on weighted scores and written answers, then weigh implementation effort and total cost. Choose the vendor whose answers held up under follow-up questions, not the one with the longest feature list. A narrower system your team adopts beats a broader one it abandons.

Putting the decision together

Write a one-page summary for your approvers covering the scores, the risks, the total cost and the implementation plan. Finance and IT are more likely to approve a decision they can trace back to written answers. In addition, record which vendor came second and why, because that note becomes useful if the first choice stumbles during contract negotiation.

If you want an HRIS that sits on top of the payroll you already run, Worknice is a sensible option to include. It suits Australian organisations of roughly 50 to 1,000 employees. It integrates two-way with Xero, MYOB AccountRight, Micropay and KeyPay, keeps customer data in Australia, and assigns a dedicated implementation manager to each customer. However, an organisation that wants payroll bundled into the same product, or that runs payroll across many countries, may prefer an all-in-one or global platform. See how Worknice connects to payroll for the direct integrations and what each one does.

Frequently asked questions

What should be on an HRIS requirements checklist?

An HRIS requirements checklist should start with your five must-haves, your workforce structure and the source of truth for each type of data. Add the payroll and other tools you are keeping, plus obligations such as Fair Work records and WGEA reporting. Finish with security requirements and approvers, and write it before any demo.

What is an HR software evaluation matrix?

An HR software evaluation matrix is a scoring table for your shortlist. It lists each criterion, gives it a weight, and scores every vendor on the same scale with a note on the evidence. Must-have criteria act as pass or fail gates. The matrix keeps the decision traceable, so finance and IT can see why one vendor won.

Do I need an RFP to buy HR software?

Most organisations with 50 to 1,000 employees do not need a formal RFP. A written evaluation checklist, scripted demos and a scoring matrix usually give enough rigour. An RFP becomes worthwhile when procurement policy requires one, when spending crosses an approval threshold, or when a board or government funder expects a documented tender process.

Does WGEA reporting apply to my organisation?

WGEA reporting applies to private sector employers with 100 or more employees in Australia, including corporate groups that reach 100 combined. Reports are lodged each year between 1 April and 31 May. Employers directly employing 500 or more people must also work towards gender equality targets, so check whether a vendor can produce the report.

Should my HR software also run payroll?

Not necessarily. Many Australian organisations keep a payroll system they trust and add an HRIS that integrates with it, rather than moving to one bundled product. Either approach can work. The deciding questions are which fields sync between the two systems, in which direction, and how much you still key in by hand each pay cycle.

About the author

Graham Martin is Co-founder of Worknice, an Australian HRIS built for mid-to-large organisations. He has spent more than a decade working with Australian People and Culture teams on HR systems, compliance and payroll integration, including many software evaluations from the buyer’s side of the table.

Related reading

• What an HRIS is, in Australian context: the category explained, including what sits inside an HRIS and what stays with payroll.
• The Australian HR tech stack: how organisations combine an HRIS with payroll, rostering and recruitment tools.
• What a WGEA-compliant HRIS does: what to look for if gender equality reporting is on your checklist.
• How to choose HR software: the step before this one, building a shortlist worth evaluating.

Sources

1. Workplace Gender Equality Agency. “Gender Equality Reporting.” WGEA, accessed 23 September 2026. https://www.wgea.gov.au/reporting
2. Workplace Gender Equality Agency. “Who needs to report?” WGEA Reporting Guide, accessed 23 September 2026. https://www.wgea.gov.au/reporting/reporting-guide/eligibility
3. Workplace Gender Equality Agency. “Reporting experience survey.” WGEA, 2025 survey results, accessed 23 September 2026. https://www.wgea.gov.au/reporting/reporting-guide/reporting-experience-survey
4. Fair Work Ombudsman. “Record-keeping.” Fair Work Ombudsman, content last updated 28 August 2026, accessed 23 September 2026. https://www.fairwork.gov.au/pay-and-wages/paying-wages/record-keeping
5. Fair Work Ombudsman. “Record-keeping and pay slips fact sheet.” Fair Work Ombudsman, content last updated 16 January 2026, accessed 23 September 2026. https://www.fairwork.gov.au/tools-and-resources/fact-sheets/rights-and-obligations/record-keeping-pay-slips
6. Australian Taxation Office. “About Payday Super.” ATO, last updated 10 August 2026, accessed 23 September 2026. https://www.ato.gov.au/businesses-and-organisations/super-for-employers/payday-super/about-payday-super
7. Office of the Australian Information Commissioner. “Data breach notifications increase to all-time high in 2025, new NDB stats show.” OAIC, 6 July 2026. https://www.oaic.gov.au/news/media-centre/data-breach-notifications-increase-to-all-time-high-in-2025,-new-ndb-stats-show